Skip to end of metadata
Go to start of metadata
The Australian Research Data Commons Party Infrastructure Project (ARDCPIP) was successfully completed in July 2011. This wiki and the documents it provides remain available for reference purposes but users are advised that is is no longer actively maintained.

Current documentation relating to the Trove People Zone is available in Trove Help. Contributors are advised to review this documentation and contact the Trove Support Team with any queries.

Additionally the Australian National Data Service (ANDS) makes available ARDC Party Infrastructure documentation specifically tailored for the research sector at: http://ands.org.au/guides/ardc-party-infrastructure-awareness.html

ARDC Party Infrastructure Project Usage Scenarios


The following usage scenarios illustrate the possible uses of the Party Infrastructure Project to a range of users from the research sector. The scenarios have been discussed by the Party Infrastructure Project Advisory Group and will assist in generating requirements for the Project. We welcome feedback which can be provided via comment on this wiki page or directly to the Project team at the National Library of Australia (see contact us for details).

Section A. User: public researcher

1.      Research Data Australia [ANDS] search

A researcher uses Research Data Australia to discover datasets about the Kartomi Collection of Traditional Musical Arts in Sumatra. She then wants to find more information about Margaret Kartomi such as works by and about her. She clicks on the People Australia public party identifier which links to an Research Data Australia party record which in-turn links to the Margaret Kartomi record in the Trove People and Organisations view.

Assumptions

A People Australia public party identifier exists for Margaret Kartomi and an associated record is available via the Trove People and Organisations view. 

The Research Data Australia dataset record links to the Research Data Australia party record.   

The Research Data Australia party record contains a People Australia public party identifier.

Clicking on the party identifier link provides the relevant page from the People Australia zone in Trove.

Requirements

Research Data Australia is able to harvest party records from People Australia. 

Research Data Australia able to display the People Australia public party identifier in their records and link to the Trove People and Organisation record. 

Data exchange format established: RIF-CS to EAC and EAC to RIF-CS mappings available.

2.      Search for Research Data Australia [ANDS] datasets

A researcher uses the Trove People and Organisations view to find the record for Margaret Kartomi. He is interested in finding more information about the Kartomi Collection of Traditional Musical Arts in Sumatra which is listed under 'resources by'. He clicks on the link for the Collection and is taken to the Research Data Australia record for the Kartomi Collection of Traditional Musical Arts in Sumatra from where he can gain access to the dataset.

Assumptions

A People Australia record exists for Margaret Kartomi and is available for viewing via the Trove People and Organisations view. 

A Research Data Australia dataset record exists for the Kartomi Collection of Traditional Musical Arts in Sumatra.

Trove has harvested records for datasets from Research Data Australia.

Requirements

People Australia is able to harvest RDA records. 

Data exchange format established: RIF-CS to EAC and EAC to RIF-CS mappings available.

3.      Author/topic search

A public researcher would like to retrieve all works published by an academic on sports physiology. The academic has changed their surname and honorific over the publishing period in addition to changing affiliation twice. The academic has published some of these articles in English and others in German. Some of the works are co-authored while others are sole authored. The researcher searches Trove for the author and topic and finds the link to the academic's record in the Trove People and Organisations view.

Assumptions

Works by or about the academic have been harvested into Trove (via Libraries Australia, Trove or People Australia).  

There is a People Australia record with persistent identifier for the academic that has captured name variants, affiliation changes and research outputs by and about the academic from harvested sources.

Requirements

People Australia currently provides for this scenario.Suitably rich data is required from all contributors to complete this scenario in all cases.

4.      Comprehensive literature search

A researcher wishes to discover all of her public research outputs irrespective of sole or joint authorship and institutional affiliation. The search is to encompass institutional repositories, databases and library catalogue records. She is able to discover the information required through a record about her in the Trove People and Organisations view.

Assumptions

Works by or about the researcher have been harvested from stated sources such as Australian Research Online and Libraries Australia by People Australia.  

There is a People Australia record with persistent identifier for the academic that has captured name variants, affiliation changes and research outputs by and about the academic from harvested sources.

Requirements

People Australia currently provides for this scenario. Suitably rich data is required from all contributors to complete this scenario in all cases.

5.      Corporate body search

A public researcher wishes to find information about CSIRO Division of Wildlife and Ecology including its preferred name, earlier and later names and related resources. He searches the Trove People and Organisations view in Trove for CSIRO Division of Wildlife and Ecology, finds the record for the CSIRO Division of Wildlife and Ecology in the results set and retrieves it.

Assumptions

A record for the CSIRO Division of Wildlife and Ecology exists in People Australia that lists corporate name variants, preferred names, earlier and later names in addition to resources by and about the division.

Requirements

People Australia currently provides for this scenario. Suitably rich data is required from all contributors to complete this scenario in all cases.

6.      Public institutional repository search

A researcher finds a record in their institutional repository on climate change evidence in Antarctica. He wants further information on the author such as biographical information and their fields of activity in addition to all research outputs they have published to date on that subject in addition to any available raw data.

Assumptions

The party record for the author is available in the Trove People and Organisations view. Contextual information such as fields of activity and biographical information have been provided to People Australia.

Requirements

The institutional repository has matched their party records in People Australia and has implemented People Australia public party identifiers (searches for their public local ids would also work).

The relevant party record exists in the Trove People and Organisations view.

A link from the institutional repository to the Trove People and Organisations view is available to the researcher.

Party information from the institution has been harvested and matched.


Section B. User: Institutional Repository Manager or Data Manager

1.    Repository submission for an identity

A Repository/Data Manager wants to create a new record in his repository for a research output produced by an academic at his institution and obtain a public party identifier to associate with the record and use the appropriate form of name.

Assumptions

The manager's repository software is capable of using the People Australia machine-to-machine interfaces to query for various forms of name and identifiers or the manager has access to Trove. The repository software can store the public party identifier and the various forms of name for the party.

                                               

The name required exists in People Australia or can be submitted to People Australia for automatic or hand matching. Candidate names (names without a public party identifier) can be matched with an existing party record or created as new party records.

Requirements

Records can be exchanged between the repository software and People Australia using standards based record formats. The repository software is able to provide records via an OAI repository. For machine-to-machine transactions support for querying via SRU or harvesting via OAI would be required. Managers have access to the People Australia Data Administration tool to undertake hand matching.

2.    Repository submission for an identity using NicNames

A Repository/Data Manager wants to create a new record for a research output produced by an academic at her institution and obtain a public party identifier to associate with the record and use the appropriate form of name.  She uses NicNames to match identities locally because some information about the parties she manages is not for public consumption but is useful for matching purposes.

Assumptions

The manager uses NicNames for managing the identity locally. NicNames is capable of using the People Australia machine-to-machine interfaces to query for various forms of name and identifiers or the manager has access to Trove. The repository software/NicNames can store the public party identifier and the various forms of name for the party.

                                               

The name required exists in People Australia or can be submitted by NicNames to People Australia for automatic or hand matching. Candidate names (names without a public party identifier) can be matched with an existing party record or created as new party records.

Requirements

Records can be exchanged between NicNames and People Australia using standards based record formats. NicNames is able to provide records via an OAI repository. For machine-to-machine transactions support for querying via SRU or harvesting via OAI would be required. Managers have access to the People Australia Data Administration tool to undertake hand matching of unmatched records in NicNames.


Section C. User: Research Office staff

1.    Cross institution search for reporting purposes

Research office staff at the University of Newcastle use People Australia to obtain details of a researcher's outputs over the past three years for use in government reporting e.g. Excellence in Research Australia (ERA) requirements. These outputs were created at the University of Newcastle and at the University of Sydney where the researcher held a previous position.

Assumptions

A People Australia record exists for the researcher.

The University of Newcastle and the University of Sydney have a record of all of the researcher's outputs (e.g. in their Institutional Repository) since his employment at the respective institution and these outputs include date of publication.

Requirements

The University of Newcastle and the University of Sydney make the researcher's outputs publicly available.

The University of Newcastle and the University of Sydney contribute the researcher's record to People Australia.

The researcher's records from the University of Newcastle and the University of Sydney have been matched into a single identity record for the Researcher in People Australia and allocated a People Australia persistent identifier. Research outputs are listed under the 'resources' section of the People Australia record.

2.    Reporting using FoR Codes

A research office staffer wishes to use People Australia to report on research outputs by a particular researcher within a particular Field of Research (FoR) code.

Assumptions

Searches by a combination of researcher (author/creator) and FoR code are possible in People Australia. 

A record exists in People Australia for the researcher. Each record of research outputs by the researcher contains reference to at least one FoR code.

Requirements

People Australia is able to harvest the public research outputs of the researcher containing reference to FoR code(s) from data contributors in the research sector.  

Section D. User: various


1.      Data correction

A user discovers inaccuracies in a People Australia record and would like the data corrected. 

Assumptions

There is a contact point at the NLA and/or the data contributor of the People Australia record for users to report issues concerning People Australia.

Requirements

The NLA/data contributor to People Australia has a contact point for users to report issues concerning their records.

The NLA has a contact point for each data contributor to People Australia to report issues concerning their records.

A data contributor is able to edit their own records.

NLA is able to harvest updated records from a data contributor.

2.      Record removal

A user would like a record removed from People Australia.

Assumptions

There is a contact point at the NLA for users to report issues concerning People Australia.

Requirements

The People Australia Data Administration module allows a People Australia record to be removed from the service or hidden from public view. 

3.    Data addition

A user would like to add information to a record in People Australia.

Assumptions

There is a contact point at the NLA for users to report issues concerning People Australia. 

Requirements

Users are able to add information to a People Australia record through a comment box or using tags.

4.    Contact details

A user finds a record for CSIRO Division of Wildlife and Ecology and wishes to contact the CSIRO researcher who authored one of the associated resources.

Assumptions

There is a contact point at the NLA and/or data contributors to People Australia for users to report issues concerning People Australia.

Requirements

Contact details for individual researchers are managed by the data contributor not People Australia.

Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
https://wiki.nla.gov.au/display/ARDCPIP/Usage+Scenarios
wiki.nla.gov.au
crawl=CC-MAIN-2015-11
88638
application/http; msgtype=response
sha1:AVH5VMWVOGYIDGDPRPFRYRTR5HM7CYYT
<urn:uuid:5c062aac-e3a3-439a-9187-b88292b8d292>
2015-02-28T01:55:09Z
192.102.239.239
sha1:QM65GBL7APLFJSXTWXGKTLW2LIKWN2H5
<urn:uuid:0bb7a626-8ade-445e-bbd7-ad3d80002d77>
https://wiki.nla.gov.au/display/ARDCPIP/Usage+Scenarios
length
response
<urn:uuid:e6250875-f85c-4906-8d82-eb933a96c9c1>
robots: classic
hostname: ip-10-28-5-156.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2015-11
operator: CommonCrawl Admin
description: Wide crawl of the web with URLs provided by Blekko for February 2015
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf