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


Post a Comment

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