- Product: Summon
How do we include an institutional repository in the Summon service?
Use the following procedures to include an institutional repository (IR) in your Summon service.
You have the option to index one institutional repository in Summon when you first implement the Summon service; after that, you can add a maximum of one IR per quarter.
The repository must support the OAI-PMH protocol for Summon to automatically harvest the content. If the repository does not support the OAI-PMH protocol, then you will need to manually upload your files via FTP. After the records have been indexed for the first time, please use the notification form in the Content Ingestion section of the Summon Admin Console to notify us of any reloads, see instructions here.
To have your repository harvested, please submit a case using the Support Portal (available from the More Sites menu above) with the following options selected:
- Asset: Summon Index
- Category: Client Content / Content Issue
- Subject: Institutional Repositories (IR)
- For the Title, enter one of the following:
- New IR -- [name of the repository] -- OAI-PMH (if the IR supports OAI-PMH)
- New IR -- [name of the repository] -- FTP (if the IR does not support OAI-PMH)
- Include the following information in the Description text box:
- Name of the IR
- Public URL to the IR
- Expected record count
- URL for the OAI-PMH access point
- Optional OAI-PMH instructions (such as separate by sets, ignore certain sets, or include all sets)
- Should the IR be publicly accessible (to all Summon customers), or only accessible to your institution's patrons?
- Does the IR have any full text records, or is it abstracts/citations only?
- How much of the IR content (whether text, image, video, audio, etcetra) is fully available online?
- 100% available via direct link from the IR interface
- Some fully available (describe which records have full text; for example, "all dissertations are full text" or "all records with a format of 'application/pdf' are full text," etc.).
- None are available (abstracts/citations only).
- Description of the repository content. For example, "Thousands of images, texts, and audio/video from ECU's diverse collections and beyond. Includes the more than 7,500 historic images from The Daily Reflector, Greenville, N.C.'s, daily newspaper, documenting the sweeping changes in Eastern North Carolina between 1949 and 1967."
- IR's Library Location (optional). Some libraries find that the Library Location facet assists users in accessing IR content. Note that one Library Location per IR is our standard practice.
Click Submit to send the request.
What happens next depends whether your IR supports OAI-PMH:
Repository Supports OAI-PMH Protocol
The Summon ingestion system will harvest all of the content from the OAI stream. After the OAI stream has been ingested, we will map the metadata and ingest the data into the Summon index.
We can use any metadata schema that your repository supports in OAI-PMH; however, we prefer to use OAI-DC, which results in faster ingestion. (See Mapping OAI-DC Fields for details.) Repositories using different schemas may take more time.
It will take approximately three to six weeks for the content to be processed and appear in Summon. After the initial ingestion, ProQuest will re-harvest the collection approximately once per week to ensure the content is up to date. If the content changes more or less frequently, please let us know when you submit the request.
Repository Submitted via FTP Transfer
After your request has been submitted, you will receive an email with instructions for uploading data from your IR to the Summon FTP server. The preferred upload formats are XML and MARC files. The data may also be submitted in tab-delimited text files with header-row field names.
Tab-delimited text files will take longer to upload and depend on the content format. Let us know if you plan to submit a tab-delimited file.
Once you have uploaded files to the FTP server, respond to the above email and let us know they are there.
The Summon metadata librarian team will map the metadata to the Summon metadata schema and then ingest the data into the Summon Index. Allow three to six weeks for the content to be processed and appear in Summon.
To maintain the content in Summon, you will need to upload new, updated or deleted records to the Summon FTP server on a periodic basis, and let us know whenever you do so. If this is not done, the content in the Summon service will become out of sync with your repository. To let us know you have submitted a new full load for your repository, please use the notification form in the Content Ingestion section of the Summon Admin Console, see instructions here.
- Date Created: 9-Feb-2014
- Last Edited Date: 27-Apr-2016
- Old Article Number: 8798