Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Data Source
Note that the input path is oai_dc:dc, despite the fact that we harvest qualified DC data.
Image Removed
Image Added


Scope

To view records in Primo, you have to create a scope, and then put that scope in a view.  The scope needs to be named the same thing as your source, because the OTB norm rules are already set up to write the source as a scope value in the PNX.

Image RemovedImage Added

Add the scope to any view where you want the IR records to be in your search results.  One Ex Libris trainer defined the scopes you build in the Views area as "scope buckets."  They're called scopes, but they're really containers of one or more scopes.  You can add your IR as a separate scope bucket so it will be searched in a separate tab/dropdown, or add it as a value to an existing scope bucket so the results are just automatically included with whatever else it's searching.

Separate scope bucket:
Image Removed
Image Added

Add to existing scope bucket:
Image Removed
Image Added

If you added it to an existing scope bucket, you're done.  If not, you need to choose which tab to put it in, click Edit, and then Add a New Scope:
Image Removed
Image Added

Norm Rules

Duplicate from Generic Dublin Core.  Start with the Orbis Cascade recommended changes.  For an example of modified norm rules (for local additions and to adapt to Qualified Dublin Core) see here:  Example of DC Norm Rules Changes for Institutional Repository Harvest

Test records:  Load a harvested file, or do this quick-and-dirty method:

...

  • Data Source:  Institutional Repository
  • Harvesting Method:  OAI
  • Server: http://[base URL]/do/oai/
  • Metadata format:  qdc
  • Set: exact name of set as found in XML header (e.g. "publication:students")
  • Start harvesting files/records from: (use date of oldest content; auto-updates to most recent harvest date)
  • Start time: (default)
  • Normalization Mapping Set:  your new norm rules
  • Enrichment Set:  No Enrichments - Template
  • Harvested File Format:  *.tar.gz
  • Include DEDUP (checked)
  • Include FRBR (checked)
  • Force DEDUP (checked)
  • Force FRBR (checked)
  • Maximum error threshold:  5% (default)

Example of Regular (harvest) pipe:

Harvest Pipe configurationImage Added

Example of Delete pipe:

Image Added

Example of No Harvest (renorm) pipe:

Image Added

Deleting a pipe:

  • A pipe that has never been executed can be deleted in the Back Office.  If the pipe has ever run, only Ex Libris can delete it–open a Salesforce ticket for this.

...

Note that a status of completed when Stage still says "harvesting" isn't necessarily an error–it can mean that there were no new records in the source available for harvesting, so the job ended there.Image Removed.

Image Added


Additional Back Office Configuration

If an extraneous and non-functional link appears in the GetIT! 2 (At the Library) section of your records, here is how to remove it without disturbing possibly necessary GetIT! 2 link functions for Alma records.

  • ADD row, ENABLED: Online Resource not_restricted 01CALS_ALMA display openurl
  • ADD row, NOT ENABLED: Online Resource not_restricted /[your data source code] display openurl
  • DISABLE row: Online Resource not_restricted ALL display openurl
  • You must ADD a row for every data source if you take this approach.

Image Added