1 / 10

ARDC Party Infrastructure Project Usage Scenarios

ARDC Party Infrastructure Project Usage Scenarios. Natasha Simons Business Analyst, ARDC Party Infrastructure Project. Scenario 1 Contributing party records to the NLA and getting a persistent identifier for these party records.

leroy-kane
Download Presentation

ARDC Party Infrastructure Project Usage Scenarios

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ARDC Party Infrastructure ProjectUsage Scenarios Natasha Simons Business Analyst, ARDC Party Infrastructure Project

  2. Scenario 1Contributing party records to the NLA and getting a persistent identifier for these party records This usage scenario allows a data manager from the research sector to contribute party records from their own institution or organisation to the NLA. It allows them to get a persistent identifier (and associated information) for these party records from the NLA for use in their local database.

  3. Preconditions1. The user (data manager) is willing and able to provide party records to the NLA via OAI-PMH.2. The user has access to the web-based People Australia Data Administration module.3. The user's software is capable of using the People Australia machine-to-machine interfaces to query for the persistent identifier or the user has access to the Trove search interface. 4. The user’s software can store the NLA persistent identifier (and associated information).

  4. Basic Course1. User (data manager) makes local party records available for OAI-PMH harvesting by the NLA.2. NLA uses its Harvester application to get the records from the user.3. The NLA Harvester applies automatic matching rules to the records to determine matches with existing People Australia identities.4. The records fail automatic matching (no matches with existing identities are found) and are then passed to the People Australia Data Administration module for human review.5. User (data manager) logs in to the People Australia Data Administration module and finds the records awaiting human review from their collection.

  5. Basic Course6. Within the Data Administration module, the user selects to create a new identity in People Australia from a record contributed from their collection.7. NLA system creates a new party identity in People Australia from the record and assigns an NLA persistent identifier (NLA party ID). The record is instantaneously made available through Trove and People Australia machine-to-machine interfaces.8. The user (data manager) selects own system to query NLA’s People Australia for the party record via machine-to-machine interfaces (e.g. OAI-PMH, SRU) or through Trove search interface.9. NLA’s People Australia returns record containing persistent identifier (and associated information) for the party.10. User allocates NLA persistent identifier (and associated information) to own record in local database.

  6. Alternative course1. NLA uses its Harvester application to get the record from the user (data manager).2.. The NLA Harvester applies automatic matching rules to the record to determine a match with an existing People Australia identity.3. The record passes automatic matching and is co-located within an existing People Australia identity. 4. The record is instantaneously made available through Trove and People Australia machine-to-machine interfaces.8. The user selects own system to query NLA’s People Australia for the party record via machine-to-machine interfaces (e.g. OAI-PMH, SRU) or via Trove search interface.

  7. Scenario 2Comprehensive search for a researcher or research organisation This usage scenario allows a user (such as a researcher) to find information about a researcher or research organisation via the NLA’s Trove/People Australia service or alternatively, via a local institution database or Research Data Australia

  8. PreconditionsThe user is able to search Trove.AssumptionsRecords about the researcher or research organisation have been contributed to the NLA (ideally from multiple sources).

  9. Basic Course – direct search of Trove1. User (e.g. a researcher) searches Trove search interface for a particular researcher or research organisation.2. Trove returns a search result containing the party identity record about the researcher or research organisation. The party record contains name entry, persistent identifier, contributor (e.g. ANDS) and may also include forms of name, occupation, fields of research, existence dates, biographical information, research outputs, selected resources by and about the party, related people and organisations. Also contains hyperlinks back to original record in each contributor’s database.

  10. Alternative Course –search of local institution/organisation database1. User (e.g. a researcher) searches their local institution database or Research Data Australia and locates a record of a dataset or research output. The record includes an NLA persistent identifier (NLA party ID) for each party associated with the work.2. User clicks on the NLA persistent identifier in the local record and is taken directly to the party record in Trove.

More Related