Thursday, 16 August 2012

Testing your NLA/Trove Party infrastructure

These instructions have just come in from National Library of Australia (NLA). They should be of interest to those people wanting to get moving on the NLA/Trove Deliverable...

Before the NLA can harvest records from a Contributor's website you will need to complete steps 1-4 in the following sequence:

Note. This may be able to be completed in a few days but may take a couple of weeks, depending on the NLA's work pressure and resources.

  1. A Contributor should have records to contribute to the NLA Party Infrastructure
  2. A Contributor can make these records available for harvest via OAI-PMH in a schema we can process (RIF-CS or EAC-CPF)
  3. A Contributor provides details to Trove of the following:
    * Contributor name:
    * Contributor ISIL:
    * Contact person:
    * Schema used for records:
    * Base URL for harvesting by NLA via OAI-PMH:
    Note. Press for links to Training and detailed instructions on ISIL codes.
  4. When this information is received Trove submits a request to the NLA's IT Section to set up the Institution as a Contributor in Trove as well as for the Trove Identities Manager(TIM) - (Note. it can take a week or more for this to happen)
  5. When this has been done the Trove team will set up the NLA TEST Harvester to do a Test harvest of the records. These records are checked for content and if changes are required the Trove team will communicate with the nominated contact person. If Trove needs to make any alterations to the transformation steps for the records, the Trove team will have to submit a request to NLA's IT support.
  6. When any issues are resolved, Trove will do a full Test harvest and pass the records through the auto-matching process and the records that pass the auto rules will be loaded to Trove TEST. The records that fail the auto match process will be loaded to the unmatched record queue in the TIM Beta system.
  7. The Contributor will then be given access to the TIM system where they can view their un-matched records so they can manually check for existing names to match against or to create new records from their unmatched records. This access requires the Contributor to be a Trove registered user, by signing up to both the Trove production service [] and the Trove Test system [] using the same user name, password and email address.
  8. If there are no issues with the records in TIM Beta and Trove Test, the Trove Team will then complete the work and do a harvest into Trove and TIM. The records will then be publically available with their NLA party identifier.
  9. Trove will then set up a schedule to do automatic incremental harvest at a time and frequency that suits the Contributor.

A party record is allocated an NLA Party Identifier when it passes the auto-matching rules in the identity service processing and is displayed in Trove's People and Organisation zone. For records that do not pass the auto-matching rules the records are loaded to the Trove Identities Manager (TIM) where manually reviewing is required. When an unmatched record in TIM is matched to an existing identity or is used to create a new identity, this record acquires a NLA identity and is displayed in Trove.

Note: TIM is the system to manage the unmatched records not the system for a contributor to add their records.


NLA will do the initial testing to make sure the records are being harvested, transformed, matched properly through the auto-matching rules and loaded to Trove.

When the NLA has them in the Trove Test and TIM Beta the Trove Team will let the contributor know and they can check to make sure their records are displaying the correct information in Trove.

Questions are welcome...


Post a Comment

Note: only a member of this blog may post a comment.