1. Remote Data Sources in Primo Ebsco API WorldCat API Local Content

2. Ebsco API Barbara Valentine, Linfield

3. Ebsco API Ebsco API is a remote source configured by Ebsco and ExLibris made available to Primo via scopes Ebsco API – can include all local Ebsco databases; select via Ebsco admin as with other “profiles. Configuration details: EbscoHost: see “EbscoHost API” http://support.ebsco.com/eit/ws.php) http://support.ebsco.com/eit/ws.php ExLibris: see "Configuring the EBSCO adapter”) in Primo Documentation.

4. Primo Central Index (PCI) PCI created and included by ExLibris to work with Primo Includes citations from vendors partnering with ExLibris No Ebsco selections currently available; but common citations (e.g. from Gale) may surface some Ebsco FT in Alma ExLib & Ebsco talks to include some Ebsco citations in the PCI; API unaffected by these talks

5. PCI surfaces Ebsco FT

6. Ebsco API vs PCI Scopes: Ebsco API and PCI can both be included in any Scope as Third Node Adaptors (in Primo Back Office) Note: Error report problem blending Ebsco API with PCI (with no local content) resolved with Primo 4.7..

7. Ebsco Only Scope

8. Third Node Adaptors

9. Ebsco API vs PCI Search Differently Facets: Results from PCI include typical faceting choices Ebsco API limited to Subject & Journal Title. Ignores other Primo facets; Problem blended with “Everything” scope (ex. a limit to books scope includes Ebsco API articles) Not sure how works with just PCI (test after 4.7?) Ebsco API results include all articles, even those with no FT (grey dot) PCI includes choice to return results “available only” with Expand Results box

10. Everything Search

11. Ebsco Only Search

12. Ebsco Only “View It”

13. Vendor Interface vs Primo Ebsco API searching via Primo not as refinable as native interface Primo default (simple) searches all fields; Ebsco All default searches indexed terms Compare Advanced Primo TX / Title limits. Cannot search specific databases Ebsco API via Primo does dedup searches like vendor Ebsco All search How many have Ebsco API?

14. Conclusions Issues remain blending Ebsco API with other scopes. We might try PCI/API blend after 4.7 Why use? All Ebsco content might combine with PCI? Separate scope for those familiar with Ebsco? No plans known for developing Ebsco API facets; Questions? Barbara Valentine, Linfield College (bvalen@linfield.edu)

15. WorldCat API Sara Brownmiller, UO

16. WorldCat via Primo WorldCat uses a third node adaptor (API) – sending a query out to OCLC and returning results into Primo The WorldCat API allows users to perform a simple search and selected types of advanced searches. Call number searching is not available in the WorldCat API. Facets are not available for searches in WorldCat No login is required to search WorldCat

17. WorldCat integration options Alliance libraries offering WorldCat keep it in a separate scope WorldCat results are not de-dupped for items owned by an Alliance library Two options for “Record from WorldCat” in results Link out to summit.worldcat.org or worldcat.org Show local holdings or offer link to interlibrary loan

18. WorldCat at Linfield

19. WorldCat at UO – item owned by UO

20. WorldCat at UO – Details tab

21. WorldCat at UO – Link out to WorldCat

22. WorldCat at UO – checked out

23. WorldCat at UO – item not owned by UO

24. WorldCat at Reed – item owned by Reed

25. WorldCat at Reed – item not owned by Reed

26. WorldCat via Primo – what’s next? Alliance libraries need full integration into Primo – ideally into institutional default scope Full functionality, including facets Ability to de-dup so only items not available at the institution or in Summit are merged into results list

27. Institutional Repositories & Primo Nathan Mealey, PSU

28. Four Components of a Pipe ●Data source ●Scope ●Normalization rule ●Pipes

29. Step 1: Create a data source Key Fields 1.Source format 2.File splitter 3.Name 4.Input record path

31. Step 2: Create a scope

32. Step 3: Create a normalization set ●Can be copied from an existing normalization ruleset ●Maps the newly created scope to the soon-to-be created pipe ●Norm rule sets must be created, then deployed, and then they’ll be available to use

34. Step 4: Create a pipe Key fields ●Pipe type ●Data source ●Harvesting method ●Server ●Metada format ●Set (optional) ●Normalization mapping set ●Dedup and FRBR

36. Running & Monitoring Pipes ●Pipes can be run manually ●They can also be scheduled ●Primo compiles a report each time a pipe runs

38. Recommendations ●Start small ●Follow examples (either from ExL or from Alliance) ●Plan your scopes

39. WU Challenges & Success Bill Kelm, Willamette

40. DSpace Collection 1. Created my new data source.

41. DSpace Collection 2. Set up the new scope value.

42. DSpace Collection 3. Set up the new pipe:

43. DSpace Collection 4. Ran the pipe to harvest the collection.

44. DSpace Collection 5. Harvested, but still no records in the Sandbox Primo. Lesson Learned: You need to run indexing on the data source (pipe). This needs to be done by someone with consortial level access. Email opened with Al & Sara.

45. CONTENTdm Collection Archives Finding Aids into Primo

46. CONTENTdm Collection Use MarcEdit to Convert EAD=>MARC

47. CONTENTdm Collection

48. MarcEditor to convert to MARC

49. CONTENTdm Collection Alma Import Profile for EADs

50. CONTENTdm Collection Primo Now Contains our Archives Finding Aids

51. Thanks! Questions/Comments Barbara Valentine, Reference/Systems Librarian (C1) Linfield College – bvalen@linfield.edubvalen@linfield.edu Sara Brownmiller, Director Library Systems (C3) University of Oregon - snb@uoregon.edusnb@uoregon.edu Nathan Mealey, Manager Library Technologies (C3) Portland State University - nathan.mealey@pdx.edunathan.mealey@pdx.edu Bill Kelm, Systems Librarian (C1) Willamette University – bkelm@willamette.edubkelm@willamette.edu