-
Notifications
You must be signed in to change notification settings - Fork 1
Administrative Home
The Harvester Administrative home page may be accessed by going to http://servername:8080/orbeon/harvester/admin/ (note the trailing slash). This is one of two XForms web pages in the backend, and it must be accessed directly via 8080 and not through the Apache web server proxy address.
Upon logging into the Admin page for the first time, the page may indicate that no sets are present in the RDF triplestore. The user will see a table containing an alphabetical listing of OAI-PMH sets that have been harvested, sorted by repository, with the count of CHOs in the system for each institution. The harvester-admin superusers will have access to see and delete any set, but members of a particular repository only have access to their own content.
The presence of repository metadata is fundamental to the functionality of the Harvester. In the right sidebar there are three options:
- Refresh Repository Metadata (only accessible to harvester-admin users)
- Enrich Creators/Contributors or Genres
- Import OAI-PMH
- Edit Repository Metadata
Select the first option to refresh the repository metadata from RDF/XML stored in the repository_records folder (default location: /usr/local/projects). The repository_records include RDF for Archives West partners and Orbis Cascade partners that participate only in the Harvester application. The Harvester config.xml file contains the path of this directory.
This interface will allow users to match literal values within dcterms:creator, dcterms:contributor and edm:hasType to the relevant vocabularies through a similar lookup mechanism as the Optional Enrichment tab in the Import interface. This interface is detailed here.
This enables users to import OAI-PMH sets into the Harvester. See separate Orbis Cascade documentation for further details.
This option is only available to those organizations that participate only in the Harvester (not Archives West). The repository name and homepage can be modified here. Edits to repository metadata modify the relevant RDF/XML file stored in /usr/local/projects/repository_records, and SPARQL/Update pushes changes into the triplestore.