Showing posts with label NLA/Trove. Show all posts
Showing posts with label NLA/Trove. Show all posts

Monday, 25 February 2013

Metadata Stores Community News #12

1. Coming events:
2. Acceptance Criteria for Metadata Stores Deliverables - a new Tab in the Metadata Stores blog.
3. The working list of Unexpected behaviours in NLA/Trove can now be found in the Resources tab of the Metadata Stores blog.

Any questions, clarifications or additions please contact Simon Pockley (03) 99020549 simon.pockley@ands.org.au.

Thursday, 21 February 2013

TIM Matching Workshop with Natasha Simons - Wed 27th Feb 2013

Don't miss this TIM Matching Workshop with Natasha Simons on Wednesday 27th February 10:00am (NSW, Vic, Tas) (9:00am Qld) (9:30am SA) (8:30 NT) (7:00am WA) via GoTo Meeting - log-in details below...(places limited to 26).

A recording of this workshop is now available (05-03-2013)

Natasha has special insights into the National Library of Australia's Party record matching processes and will not only be demonstrating how to match real records in real time but will also share her experiences of the way in which Griffith University has gone about managing the matching process.

  • Setting up for harvesting of party records by the NLA
  • Signing up for access to Trove Identities Manager (TIM)
  • Hand matching records using TIM - demonstration
  • Getting NLA identifiers back, putting them in the metadata store and providing these to RDA
  • Summary of experience (successes, problems)

TIM (Trove Identities Manager) is the NLA's tool used for the maintenance of records in the party infrastructure. It enables authorised staff from institutions and organisations who contribute party records to the party infrastructure, to manage these records.

To get the most out of this workshop you should be familiar with TIM training modules and the National Library of Australia's Guide to managing records in the party infrastructure

See also Matching rules - Trove Party Infrastructure rules for auto-matching party record for Trove.

How to access this workshop

1. Please join my meeting.
https://www4.gotomeeting.com/join/902515079

2. Use your microphone and speakers (VoIP) - a headset is recommended.

Or, call in using your telephone.

Dial +61 2 8355 1031
Access Code: 902-515-079
Audio PIN: Shown after joining the meeting

Meeting ID: 902-515-079

Monday, 11 February 2013

NLA/Trove - unexpected behaviours: Wed 13 Feb 10:00am (Melb Time)

Recent experiences with the NLA/Trove test environment have resulted in a working list of unexpected behaviours. Most need some form of explanation.

We'll be talking through this list on Wednesday 13th February 2013 10:00am (NSW, Vic, Tas) (9:00am Qld) (9:30am SA) (8:30 NT) (7:00am WA) via GoTo Meeting - log-in details below...(places limited to 26).

N.B. This is a working list - please contact Simon Pockley about any amendments or additions you would like to make.

  1. Testing environment

    TIM Beta is the system that NLA use to check the accuracy of records before they are loaded into production. It isn’t a development system. There are limitations to the testing environment.

    a. The test NLA records cannot be deleted, so tests cannot be rerun and new people need to be created and used each time.
    b. NLA ID in TIM Beta resolves to Trove Production rather than Trove Test. This can prompt concern/confusion that valid NLA ID's might be incorrectly being ascribed to real researchers and then published on the web.

    Status - no action. The testing environment in TIM Beta does not impact on the production environment

  2. Access to TIM

    a. Access to TIM is on an individual basis without a generic link to the institution.
    Status - work-around. Establish a convention for managed usernames and passwords, for example, “ANDS.tim.matching01”, “ANDS.tim.matching02”, etc. for multiple users. A single sign-on could be established, remembering that multiple users cannot login to TIM with the same user name and password simultaneously. Generic usernames and email addresses will allow usernames to be reassigned and the password rese
    b. Also having to create individual IDs for Trove and TIM (and making these the same for the test instances of each) is cumbersome compared to AAF access to Research Data Australia.

    Status – No action. Signup to Trove is open to any user of Trove, not just those with access to the Australian Access Federation (AAF) credentials. One username and password is used for both Trove and TIM (production and test).

  3. Transparency of record status

    There’s no indication whether records have been auto-matched or gone into TIM for manual matching.

    Status - work-around. Checking which records are in TIM waiting for matching is a manual process.

  4. Identifiers lose their type

    Identifiers lose the type indicated in the contributor party record e.g. "scopus". Even NLA supplied party identifiers become type="contributor’s ISIL code".  Any identifiers and the key supplied in a contributor party record to Trove become type="contributor’s ISIL code" in the Trove party record.
    Status – low impact - no action

  5. Single element names not harvested

    RIF-CS schema guidelines state that <namePartType> is optional. The reason for variation in how names are presented is that GeoNetWork uses ISO 19115 and/or ANZLIC as its native schema which allows free text entry of names in a single element. RIF-CS party records type person that have origins in either ANZLIC or ISO19115 will be not be harvested by TROVE due to the lack of <namePartType>. Note that this issue impacts on Party person records only. Group records without <namePartType> will be ingested by Trove.
    Status – low impact - no action

  6. NLA converts keys to RDA URLS

    Not all institutions maintain or even create public profile pages. These are used as Source URLS in a Trove record.

    Status - work-around for where there are no source URLs for staff profiles is to use an optional function in Trove. If option is set to ‘on’ the entityID (Source URL) for a university's records in Trove are transformed to ANDS URLS. Trove uses a predefined URL structure to convert keys to a link to RDA and not to the researcher’s web page on the university web site. If set to ‘off’ Trove will use the source URL provided.

    For ReDBox/Mint users:

    Care should be taken that the source URL does not resolve to MINT which requires a logon, and not to a local party record as might be expected. Apply the workaround indicated above, as required.

  7. Vanishing records

    As reported by UQ:  A feed of party records was harvested but some of the records neither appeared in Trove nor in TIM - they vanished without a trace. The harvest operation did not fail, since other party records from the same harvest of the feed appeared in TIM or were automatically matched and appeared in Trove.
    Status - behaviour yet to be replicated

  8. Broken links when Researchers leave an institution (tombstone records)

    There is a need for Policy development regarding Researchers who move or even die. NLA has no control over contributor’s source links. Some universities will use the links to the researchers' local profile as the source URL. However, these links may not be maintained after the researcher leaves the universities. So in the long run there will be a lot of broken links in Trove.

    NLA comment: There is no need for a University to delete the record for a researcher when they move away from that institution. The NLA party identity is a container record and so can contain records from different universities for the same researcher. This is where some descriptive information would be valuable in the record e.g. “Left University of ZX in 2011”.

    Status – low impact - no action

  9. Inconsistent matching algorithms

    Testing Trove's automatic matching algorithms are behaving unexpectedly:

    Issue first raised by Hoylen Sue at UQ - as follows

    Situation #1: party records are harvested for the first time. That is, Trove does not contain any party records with these RIF-CS keys.

    Situation #2:  when these unchanged party records are re-harvested. That is, Trove already has existing party records with these same RIF-CS keys. In this situation UQ has found the two party records for Watson and Drebber pass "Matching Rules Part A" and replace the existing party records -- which is the correct behaviour. But the party record for Holmes does not match and goes into TIM Beta -- which is not correct. It should have been automatically matched just like the other two. Neither us nor NLA have figured out why Holmes is treated differently.

    NLA comment:

    Paul has checked this problem as much as he can and when he sends the record to TIM manually it matches. Essentially the way he's doing it is exactly the way the harvester would send the records to TIM so we have no idea why the records aren't matching when we harvest them. Paul says we need more data to work with and he's reluctant to use your data as then you won't be able to use it. Perhaps if we had lots more test records to work with we might be able to see a pattern. Sorry I don't have a solution or a reason for the records not matching.

    Status - behaviour yet to be replicated

  10. Complex matching rules

    There is an assumption that if local party records contain the NLA identifier as an identifier, then matching will occur automatically, but this is not necessarily the case. The matching rules are complex and deliberately conservative. Records which fail Part A of the matching rules then go to Part B where the NLA identifier is just one of the match points.

    Rules for matching party records: https://wiki.nla.gov.au/download/attachments/24379936/ARDCPIPMatchingRulesSpec-+Ver+2.0++20+Jan+2012.doc?version=1&modificationDate=1333064788000

    From the matching rules:

    The purpose of Part A: to decide if two records are actually the same record
    An incoming record is checked to determine if it has the same contributor ISIL and record ID as a record in Trove.

    If it does, a sanity check is applied. If the incoming record passes the sanity check, it is automatically matched and overlays (replaces) the matching record in Trove. If the incoming record fails the matching rules in Part A then matching rules in Part B are applied.

    The purpose of Part B: to decide if a record should be part of an existing identity.

    The rules specified in Part B are applied to an incoming record that has failed the matching rules specified in Part A.

    An incoming record is checked to determine if it has an NLA persistent identifier. If it does, a sanity check is applied and must be passed for a match to occur.

    Incoming records that fail the matching rules specified in Part A and B are passed by the identity service to the unmatched record queue for human review for matching or new record creation in TIM

    Example:

    A university creates a record for “Davies, Peter” containing the NLA party identifier for the existing Trove record for “Davies, Peter Eric” (the Trove record was contributed by Libraries Australia, ISIL code AU-ANL:PEAU).

    Result: Part A matching rules apply, but neither ISIL code or recordID match so Part B rules are applied.

    In the Part B matching rules the system looks at the incoming record for the NLA party identifier and the NLA’s ISIL (AU-ANL:PEAU) and the NLA party identifier, recorded in control/sources/source/objectXMLWrap.

    If the university added the NLA party identifier for “Davies, Peter Eric” and the NLA agency code to the incoming record, the system would run the sanity check. It would match on Davies, on Peter, but it wouldn’t find Eric in the incoming record and so the name would fail the matching rules. Because there is always the risk that a mistake could be made when the NLA party identifier is manually entered into another organisation’s record, the system has to be certain it’s the same person so it will always check all name parts and all name parts have to match.

    Result: In this example, if the names didn’t automatically match then the record failed the sanity checks at some point.

    Status –investigate. The example above explains why records containing an NLA party identifier will not necessarily match even though they have the same NLA Identifer.

  11. RIF-CS 1.4 mapping to EAC-CPF (Encoded archival context for corporate bodies, persons and families)

    There is currently no separate overarching application profile document for NLA use of EAC-CPF. The NLA maintain mappings from MARC and RIF but these are both in flux at present as the NLA make changes to support RDA and RIF-CS 1.4.The mapping for RIF-CS 1.4 is finished but NLA’s IT is still to finish doing the style sheet to convert the records.

    Status – in progress

  12. Name sequence or name order

    The order in which names are entered is important because the Trove System has its own way of processing first name and last name. Best to enter in natural order i.e. first name: Jane, last name: Smith

    Status – work-around
---------------------------------------------------
1. Please join my meeting.
https://www4.gotomeeting.com/join/902515079

2. Use your microphone and speakers (VoIP) - a headset is recommended.

Or, call in using your telephone.

Dial +61 2 8355 1031
Access Code: 902-515-079
Audio PIN: Shown after joining the meeting

Meeting ID: 902-515-079

Tuesday, 22 January 2013

Wednesday: Amir Aryani will answer your Trove questions (Coming) What happens when you've built your Metadata Store?

1. Amir Aryani will be available to answer and NLA/Trove questions following Hoyken Sue's presentation last week.

Wednesday 23rd January 2013 10:00am (NSW, Vic, Tas) (9:00am Qld) (9:30am SA) (8:30 NT) (7:00am WA) via GoTo Meeting - details below


2. Coming - Natasha Simons will be discussing how the team at Griffith University overcame challenges associated with their Research Hub.

Wednesday 30th January 2013 10:00am (NSW, Vic, Tas) (9:00am Qld) (9:30am SA) (8:30 NT) (7:00am WA) via GoTo Meeting - details below

This discussion will include:

  1. what to do with dirty data?
  2. getting support
  3. getting access to data from different systems
  4. finding new sources of data to input into your metadata store (e.g. our theses database)
  5. what happens when your metadata store solution starts to compete with your publications repository?
  6. developing a sustainability plan to get long-term support for the Hub post-project completion that might be useful to share.

1. Please join my meeting.
https://www4.gotomeeting.com/join/902515079

2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Dial +61 2 8355 1031
Access Code: 902-515-079
Audio PIN: Shown after joining the meeting

Meeting ID: 902-515-079

Thursday, 10 January 2013

Testing NLA/Trove Identifiers - how to succeed! (16/01/2013)

Don't miss this if you want to know more about minting and testing NLA/Trove Identifiers?

Hoylen Sue (University of Queensland) has done it and will be sharing his experiences with the Trove testing environment. Hoylen is in a unique software agnostic position to explain the process because of UQs component approach to developing their Metadata Store. He has rigorously clarified every aspect of the NLA Identifier process.

When? 10:00am (NSW, Vic, Tas) (9:00am Qld) (9:30am SA) (8:30 NT) (7:00am WA) Wednesday 16th January 2013 via GoTo Meeting:

1. Please join my meeting.
https://www4.gotomeeting.com/join/902515079

2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone.

Dial +61 2 8355 1031
Access Code: 902-515-079
Audio PIN: Shown after joining the meeting

Meeting ID: 902-515-079

Tuesday, 18 December 2012

Metadata Stores Community News #10

Apologies for any cross-posting

1. Congratulations! Overview of 2012: 22 Metadata Stores Projects with 22 start dates, Software choices: 13.5 ReDBox (0.5 is using Mint), 4 VIVO, 3 homegrown, 1 ORCA, 20 Steering Committees with 129 data management champions.

2. NLA/Trove registrations: A reminder of the link to the instructions for setting up an account for contributing records to the Trove and that you cc simon.pockley@ands.org.au in to your communications with the NLA. You can expect the TIM training session to be in mid-January (date to be announced).

3. ReDBox users: Duncan Dickinson has provided an overview of what ReDBox delivers with respect to Metadata Stores deliverables. More work is scheduled that will help fulfil requirements so it'd be worth looking at the overview and chasing up information you may need for your project. Please check and let Duncan know of edits/issues. You can even add comments to the document (pls put your name in the comment so that he knows where it came from).

4. Regular Clinics: The next Wednesday Metadata Stores surgery/clinic will be held on Wednesday January 9th 2012 at 10:00am (Melb time)- a reminder will be sent out on the Monday before with the log-in details.

Seasons Greetings to everyone and best wishes for the coming year...

Simon

Thursday, 13 December 2012

NLA Trove registration

If you have not yet registered with NLA/Trove please review the registration steps outlined in the post on Friday 7th December 2012.

Important new step: When you send emails to the NLA please cc simon.pockley@ands.org.au

The reason for asking that you do this is so that we (ANDS) can have a sense of who is doing what and when. That way we can time our training workshops to meet your needs and facilitate resolution of any delays you might be experiencing.

Best wishes

Simon

Tuesday, 11 December 2012

Reminders: GoTo meetings: Today - Tues 11th Dec and Wed 12th Dec

Please remember

the RedBox NLA/Trove walkthrough is Tuesday 11th Dec 12:00pm (Melb time) see previous post for log-in details.

and

the regular Wednesday drop-in is Wednesday 12th Dec 10:00am (Melb time) see previous post for log-in details

Friday, 7 December 2012

How to set up your NLA Trove Account

For those who have yet to set up their accounts with the National Library of Australia (NLA), here is a reminder of the process.

There are prerequisites that must be met before contacting NLA.

  1. Have your ISIL code and contributor name
  2. Have records ready for harvesting (very important)
  3. Have a harvesting point
  4. Records are either in RIF-CS or EAC-CPF
  5. Records should be available for harvest via OAI

Please be familiar with these training modules. Any questions, please ask.


From the NLA’s perspective you are the Contributor. To get your party records into Trove, the basic process - in sequence is:

  1. You, the Contributor, have records to Contribute to the NLA Party Infrastructure
  2. The Contributor makes these records available for harvest via OAI-PMH in a schema that the NLA can process (RIF-CS or EAC-CPF)
  3. The Contributor provides to Trove the following details:
    • Contributor name
    • Contributor ISIL
    • Contact person
    • Schema used for records
    • Base URL for harvesting by NLA via OAI-PMH
  4. With this information the Trove submits a request to the NLA’s IT Section to set up the Institution as a Contributor in Trove and the Trove Identities Manager (TIM) - (this can take a week or more 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 you.
  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 and the records that fail the auto match process will be loaded to the unmatched record queue in the TIM Beta system.
  7. The Contributor can then be given access to the TIM system to 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 ( http://trove.nla.gov.au/) and the Trove Test system (http://trove-test.nla.gov.au/) using the same user name, password and email address.
  8. If there are no issues with the records in TIM Beta and Trove Test , we will then complete the work and do a harvest into Trove and TIM, where the records will 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 in the 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, then this record acquires a NLA identity and is displayed in Trove.

Some useful documentation about the process for a Contributor to get their records into the Party Infrastructure is on the NLA wiki page . See the ‘Contributor Guide to the Party Infrastructure’.

If you have questions or just need clarification then,
  1. Submit your enquiry through the Trove Contact us form and indicate your question is about contributing People records.
  2. Contact Simon Pockley 03 99020549, 0418575525 or Julie McCulloch 03 9905 6275,
    0412 673 335 or Amir Aryani 02 6125 0586, 0478 401 224

Thursday, 6 December 2012

ReDBox: Walk-through Curation Process: Tues 11th Dec 12:00pm AEDT

Toby O'Hara (UWS) has organised a walk-through of the curation process that is built into ReDBox, with an emphasis on the NLA-ID component where the Mint passes records to Trove/NLA and receives an NLA-ID back.

If you are interested in what ReDBox/Mint does out of the box, and the minimum configurations that are required to get NLA integration working - then this is for you.

Toby is expecting this to be a fairly technical discussion, relevant to the code and what code does what functions. Important to note: if anyone has rewritten the code with major customisations, and is having trouble, that's for a separate discussion.

Even if you've done this before, it might be worth joining in the conversation and adding tips and pointers that you have experienced yourself (UoN looking at you).


How to participate

1. Please join my meeting, 11/12/2012 at 12:00 PM AEDT.

https://www4.gotomeeting.com/join/199948127

2. Use your microphone and speakers (VoIP) - a headset is recommended.

Or,

call in using your telephone. Dial 61290873701 Access Code: 199-948-127
Audio PIN: Shown after joining the meeting
Meeting ID: 199-948-127

GoToMeeting® Online Meetings Made Easy®

Not at your computer?

Click the link to join this meeting from your iPhone®, iPad® or Android® device via the GoToMeeting app.

Wednesday, 21 November 2012

New link between ANDS Demo and Trove Test

We are pleased to inform you that the new link between ANDS Demo (demo.ands.org.au) and Trove Test (trove-test.nla.gov.au/people) is now functional. This link makes the party records in Trove Test visible to ANDS Demo, and as a result you can test how your records in Trove Test will appear in ANDS Demo. The complete test for NLA integration workflow (ANDS Workflow 1) includes the following steps:

  1. Set up an OAI-PMH interface for Trove Test harvest.
  2. Add one or more party records through the OAI-PMH interface to Trove Test.
  3. Resolve unmatched record(s) in TIM Beta (https://www.nla.gov.au/tim-beta/app). At the end of this step you should be able to see your records in Trove Test.
  4. Retrieve the NLA party identifiers using Trove API (https://wiki.nla.gov.au/display/ARDCPIP/Party+Infrastructure+APIs) (link updated 20-02-2013) or for the purpose of this test you can find them manualy by searching the name of the party records in Trove Test.
  5. Set up an OAI-PMH interface for ANDS Demo.
  6. Add one or more collection records to ANDS Demo with the NLA party identifier as the key in the related object element of these records.
  7. After 24 hours the NLA party records should appear under the NLA group in ANDS Demo (http://demo.ands.org.au/search#!/p=1/tab=All/group=National Library of Australia), and they will be linked to the collection(s).

Wednesday, 14 November 2012

NLA Trove waypoints and TIM workshop/webinar

At eResearch 2012 it was suggested that ANDS conduct a Workshop/Webinar on matching names in the Trove Identities Manager (TIM). We are now attempting to get the timing right so that this workshop comes at a time when you are ready. We need to see where you are up to.

There would appear to be five waypoints where you have:

1. Completed Trove registration

2. Integrated into the Trove test environment
You may also recall a post relating Testing your NLA Party Infrastructure.


3. Integrated into Trove production


4. Retrieved NLA Identifiers
  • To complete this you should have retrieved one or more NLA identifiers and stored them in your local systems.

5. Supplied ANDS with the linked collections to NLA identifiers
  • To complete this you should have provide ANDS with the NLA identifiers in one of the following forms:
    • Workflow 1: as a related object to a collection, or
    • Workflow 2: as an identifier for a party record

Please let me know [simon.pockley@ands.org.au] where your project is up to. I will follow with an email reminder.






Monday, 12 November 2012

A short note about ORCID, ANDS and the NLA

The ORCID identifying space is not the same as the NLA/Trove space, and each has different functionality and will serve different purposes. For example, the former would be useful for researchers who may wish to have multiple identities and the latter more useful for institutions seeking an authoritative ID.

ORCID only launched in production a few weeks ago. If you have had a play with ORCID you would have seen that some of the functionality is 'in construction'. ANDS is planning to support it in our identification infrastructure next year. 'Under the hood' - ORCID Identifiers are actually International Standard Name Identifiers (ISNI) and the two organisations (See ISNI and ORCID) are also working through any issues of complementary models and shared approaches. Identities from the National Library of Australia have already been uploaded to the ISNI space.

In the meantime, ORCID identifiers can be included as Identifiers in Party records (for Research Data Australia) where appropriate. There has been a request to Services to include ORCID as an Identifier type

Wednesday, 5 September 2012

Metadata Stores Community News #7

  1. New guidance for D4 (NLA/Trove Identifiers)
    Connecting researchers to their data is much easier if researchers are uniquely identified. ANDS partnership with the National Library of Australia (NLA) to develop a National Party Infrastructure to provide persistent Identifiers for people and groups (Parties) is realised in Deliverable 4: demonstrated alignment of records about Parties with the ARDC Party Infrastructure…

    In response to your requests for a more quantitative goal for D4, ANDS recommends that Metadata Stores projects aim to:
    • include NLA Party Identifiers for the ARC/NMHRC grant investigators that have been started after 1st January 2009 and that you create and maintain NLA identifiers for the researchers whose research data is already published in Research Data Australia (RDA);
    • (…for those wanting to extend the reach of their projects) include Party Identifiers for grant recipients for the last 10 years. This extended coverage will enable institutions to develop a richer research portfolio based on award history.

    A recent survey 16 universities with Metadata Stores projects by Amir Aryani (ANDS) indicates that the numbers of Grant Investigators (2007-2010 - where investigators are counted once for each institution) should be easily manageable. Examples: RMIT 76, Deakin University 57, Griffith University 127,
  2. ReDBox collaboration meeting in South Australia
    A meeting is scheduled for 10am on Friday September 7 in the eResearch VisLab, Room 119 in the Physics Building at the University of Adelaide to discuss a possible collaboration around the mandatory deliverables as well as Integration with Research Master. For more details contact Andrew Williams [andrew.williams@ands.org.au] mobile: +61 410 221 647.
  3. 3 Minute Video: Duncan Dickinson describing ReDBox

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 [http://trove.nla.gov.au/] and the Trove Test system [http://trove-test.nla.gov.au/] 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.

Testing:

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...

Friday, 3 August 2012

Metadata Stores Community News #6

  1. Metadata Stores - fortnightly Q & A: Is there any interest in having a fortnightly Q & A (Tele or video conference) where project issues can be discussed? FAQs are in currently being assembled for your comment.

  2. Acceptance Criteria for required Deliverables: [press link] (thanks to Vicki Picasso and Alan Glixman for prompting discussion about these criteria).

  3. Bi-directional links in Research data Australia (RDA) to external related objects:Your input?

    The ability to opt-in or opt-out (in RDA) to bidirectional links to external objects was developed form a rationale where a data source was considered to represent one authority of information. If a link inferred from one authority is displayed within information obtained from another, there is a risk of mis-attribution of information. Currently, the default for automatically enabling two-way links in your own data source is 'on and the default for automatically enabling two-way links for external data sources is 'off’. ANDS is considering changing the opt-in/opt-out function so that bidirectional links for related Parties (internal and external) are always generated. We ask for your comment on either removing the opt-in/opt-out function or, making the default choice 'opt-in' but retaining the ability to 'opt-out'. Comments please.

  4. Sharing Cross Walks, Mappings and XSLTs: [press link]

    This is a forum for sharing and discussing semantic mappings and crosswalks in any state of development. Many ANDS partners find that schema mapping is a difficult step in completing their ANDS projects, and it is helpful to see how other people have approached the task. If similar schemas are being used, existing crosswalks may also provide a head start in the development process, if the original creator is willing to allow such use.

    If you are posting a crosswalk, please include the following information either in your post or within the crosswalk itself: names and versions (or profile or element set details) of the source and target schemas, a URL if the crosswalk is available publicly, and any restrictions on how the crosswalk can be used.

  5. Featured question: Is it mandatory or optional to provide Party records to Research data Australia (RDA)? (thanks to Hoylen Sue - UQ)

    At least one party record needs to be related to each collection described in Research Data Australia. Collection records connect to Party records using the local party record key or (preferred option) by including an NLA party identifier in their related object element. NLA identifiers are entered in the RIF-CS identifier element of local party records (type="AU-ANL:PEAU"), and as a key in the RIF-CS related object element of activity, collection and service records.

    Since the preferred model is to send party records directly to NLA Trove (instead of via RDA), then sending collection records to RDA with the NLA Party Identifier embedded in them will be sufficient. RDA will then source a Party record from NLA Trove.

    See link: Best practice for creating party records
------------------------------
Best wishes
Simon

Metadata Stores: Acceptance criteria for required deliverables

Principles:

  • ANDS requires a Project Plan early in the project, in order to finalise project scope, choice of software and to confirm appropriate resourcing and planning;
  • If a project is embarking on metadata stores without existing infrastructure, then ANDS will not require delivery of the complete metadata store, nor all the deliverables depending on it - until the end of the project.
  • If a project is embarking on metadata stores with existing infrastructure, then ANDS expects that there will be a feed of records supplied to RDA (see Deliverable #1) by the middle of the project.
  • Remaining mandated deliverables are likely to have multiple dependencies on other software and organisation units, so ANDS will not require delivery until the end of the project.
  • ANDS encourages project to schedule deliverables earlier than agreed in the project description where possible.
  • Because there is likely to be a lengthy period between the Project Plan and other deliverables, ANDS requires regular and frequent progress reporting - every three months. Reporting will be lightweight, just a couple of pages, but ANDS needs to monitor progress closely, given that these are infrastructure projects with a large number of dependencies.
  • For consistency, ANDS is maintaining a ratio of payments across all projects of 25% each payment period.
D1
A working feed of records describing Collections and associated Activities, Parties and Services to Research Data Australia, in the current version of RIF-CS (1.3), demonstrated to meet the quality requirements for RIF-CS records as set by ANDS.

Acceptance: If the project is using an existing technology* then this feed is expected around the middle of the project. The feed will be confirmed by an inspection (by CLO*) of a sample of nominated records in Research Data Australia. If the technology is bespoke then an expected date should be included in the Project Plan. 

*Existing technology means that there is already a working Metadata Store.
*CLO = Client Liaison Officer (ANDS.
D2
A feed of collections from at least three distinct Faculties (or equivalent organisational units) within the institution to Research Data Australia. 

Acceptance:  This spread across Faculties is intended to support an institution-wide approach. The feed can be automated or manual.  The 3, or more, Faculties (or equivalent) will be confirmed by an inspection (by CLO) of a sample of nominated records in Research Data Australia.  An expected date should be included in the Project Plan.
D3
Demonstrated alignment of metadata records about Parties with an institutional name authority (HR or Library), with the authoritative form of the name sourced external to the metadata store, and with new researcher descriptions added to the metadata through regular updates from the name authority.

Acceptance: This interface between one or more nominated sources of party record details and the Metadata Store is expected to be confirmed by a statement of achievement by Project Manager.  Specifically, this will be demonstrated by an alignment of metadata records about parties with an institutional name authority (HR or Library), with the authoritative form of the name sourced external to the metadata store as well as new researcher descriptions added to the metadata through regular update from the name authority be confirmed by written statement by project partner. An expected date should be included in the Project Plan.
D4
Demonstrated alignment of metadata records about Parties with the ARDC Party Infrastructure Project, with researcher descriptions contributed to the NLA, and with People Australia identifiers for researchers recorded against researchers.

Acceptance:  Alignment with the NLA Party Infrastructure will be demonstrated by an inspection (by CLO) of examples of records using NLA Identifiers in Research Data Australia, as nominated by Project Manager.  An expected date should be included in the Project Plan.
D5
Demonstrated alignment of metadata records about Activities with institutional and external sources of truth (Research Office, ARC and NHMRC grant registries), with the authoritative description of the Activity sourced external to the metadata store, and with new researcher project added to the metadata through regular updates from the sources of truth.

Acceptance:   Integration with the ANDS records derived from the Grants Registries will be demonstrated by inspection (by CLO) of nominated examples of Activity records.  An expected date should be included in the Project Plan.


See updated criteria for this Deliverable
D6
Demonstrated workflow for registering new Collections in the university; this can include automated update, or semi-automated (notification-based).

Acceptance:    This will be demonstrated by a document description (with schematic) of the workflow that includes some form of alert or notification that a new collection has been, is being, or is about to be, created. An expected date should be included in the Project Plan.
D7

A software system to realise deliverables D1–D6 (and D8, D13–D14 if applicable), with robust storage and management of metadata.

Acceptance:  ANDS does not intend to assess software code already assessed or approved e.g. ReDBox, VIVO. A detailed diagram(s) of the working metadata store with associated use-case(s) will be used to assess the deployment by the ANDS Technical Assessment Group and will be shared with ANDS partners  (note - please insure that these diagrams are licensed as CC BY).
D8-D13
Optional Deliverables

Acceptance:  ANDS expects each institution to choose at least one optional deliverable. Progress of chosen optional Deliverables is expected to be included in the ANDS Progress Report Template.

Friday, 13 July 2012

Metadata Stores Community News #5

  1. Welcome to the Metadata Stores blog. The purpose of this blog is to provide a national communication channel for the MetaData Stores Community. Please inspect the tab for Funding Rules as well as the comparison of solution schematics. If you would like to post to this space please contact Simon Pockley for author permissions.

    Screenshot of the Australian Libraries Gateway where you can look up your ISIL code

  2. Action #1: Please follow this link to instructions on how to check your ISIL code, contributor name. You will need to confirm both, as well as the contact person e.g. AU-QGU, Griffith University j.morris@griffith.edu.au - You can confirm by comment box, at the bottom of this post, or email to simon.pockley@ands.org.au.

    Action #2: Please also send a Harvest URL from which the NLA can retrieve your Party records. If you are not yet ready for this then please say 'not ready' or decide on the url that you intend to use.

    See Training below - questions - just ask...

  3. All TIM/Trove training modules are at: http://ands.org.au/training/trove/index.html. Modifications to TIM/Trove training Module 1: now split into 2 parts:
    • Module 1-A: Process for contributing party records to Trove and how to obtain an ISIL code. This module explains:
      • The process for contributing records to Trove
      • How to obtain an ISIL code (International Standard Identifier for Libraries and Related Organisations)
    • Module 1-B: Register with Trove and access TIM. This module explains:
      • How to register with Trove; and
      • How to access TIM ( Trove Identities Manager).
      • TIM Beta and Trove Test
      • TIM Production and Trove People and Organisations zone
  4. We now have 2 communities of practice who have agreed to regular Teleconferences: First the ReDBox collaboration, co-ordinated by Vicki Picasso (see contact list). Second, a VIVO Group co-ordinated by Simon Porter (see contact list). More detailed information about the working sub-groups of these communities will follow.

  5. A South East Queensland Metadata Stores Roundtable is scheduled for Thursday 19th July 2012 form 10:00am - 12:00pm. The agenda is reasonably open and the session will be informal to promote discussion.

    Note the venue will now be Room 712 of the QUT library (V Block), not 714 as originally advertised. For more, contact Andrew White [andrew.white@ands.org.au].
    • Introductions and update from each of the Metadata Stores Projects?
    • National level activity update from ANDS
    • Commonalities and synergies
    • DOI's
    • NLA Integration
    • Other topics

Contributors