View unanswered posts | View active topics It is currently Sat Apr 20, 2019 7:40 am

All times are UTC + 10 hours [ DST ]




Reply to topic  [ 2 posts ] 
Add an existence dates element to the schema 
Author Message
ANDS Staff
User avatar

Joined: Thu Feb 10, 2011 11:18 am
Posts: 76
Suggested schema change
Add an existence dates element to the schema for each class of registry object which can record the start and end date of the entity being described.
The meaning of these dates will be different depending on the class of the registry object e.g.
• For person (birth, death)
• For group (establishment, incorporation, dissolution)
• For research project (start, finish)

Problem this suggestion addresses

The most urgent problem is that the current RIF-CS schema has no support for recording the existence dates for parties, in particular birth and death dates for persons. This has a significant impact on the Party Infrastructure project as authors in library catalogues often have their birth year recorded and some data providers can supply birth years for researchers. This will dramatically reduce the time they need to spend manually matching/minting party Identifiers for their researchers.
There is structured information about research grants such as their initial year and final year which is currently just mashed into description fields. The existence of this date element would allow these dates to be recorded and used in searching/filtering e.g. search only for completed projects

Identified by
Basil Dewhurst (NLA,) Monica Omodei (ANDS)

RIF-CS schema components affected
registryObject (new element – not mandatory)
Although only existence dates for party and activity registry objects have been identified as examples, existence dates for collections and service records might be relevant.

Impact on content providers
Feeds do not need to be changed as this change is backward compatible. However those data providers who want to provide this information from their systems will need to redo their export code.

Pros
More information about parties and activities can be recorded structurally. Identity matching can be far more automated for some data providers.

Cons
Another element for data providers to consider in their export systems.
Another element to be documented in the Content Providers Guide.
As it is a structural change to RIF-CS database changes will be required as well as changes to the ORCA code-base and Research Data Australia interfaces.

Technical options
Examples:
    <party type="person">
      <identifier type="AU-ANL:PEAU">http://nla.gov.au/nla.party-234234</identifier>
      <name type="primary">
        <namePart type="given">Mary</namePart>
        <namePart type="family">Woods</namePart>
      </name>
      <existenceDates>
        <beginDate>1976</beginDate>
      </existenceDates>

    </party>
    <activity type="project">
      <identifier type="purl">http://purl.org/au-research/grants/arc/DP74234</identifier>
      <name type="primary">
        <namePart>Analysis of impact of serotonin uptale inhibitors on symptoms of bi-polar disorder in young patients</namePart>
      </name>
      <existenceDates>
        <beginDate>1999</beginDate>
        <endDate>2002-06</endDate>
      </existenceDates>
    </activity>

The schema notation for this element would read as follows:
    <xsd:element name="existenceDates" type="existenceDateType" minOccurs="0" maxOccurs="unbounded">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">
        Element for holding a start date and end date.
        </xsd:documentation>
      </xsd:annotation>
    </xsd:element>

With the following type definition:
With the following type definition:
<xsd:complexType name="existanceDateType">
    <xsd:sequence>
      <xsd:element name="startDate" minOccurs="0" maxOccurs="1">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="dateFormat" use="required" type="xsd:string">
                <xsd:annotation>
                  <xsd:documentation>The format of the date element.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
      <xsd:element name="endDate" minOccurs="0" maxOccurs="1">
        <xsd:complexType>
          <xsd:simpleContent>
            <xsd:extension base="xsd:string">
              <xsd:attribute name="dateFormat" use="required" type="xsd:string">
                <xsd:annotation>
                  <xsd:documentation>The format of the date element.</xsd:documentation>
                </xsd:annotation>
              </xsd:attribute>
            </xsd:extension>
          </xsd:simpleContent>
        </xsd:complexType>
      </xsd:element>
    </xsd:sequence>
</xsd:complexType>


Tue Jun 28, 2011 1:04 pm
Profile
ANDS Partners
User avatar

Joined: Sun Jun 06, 2010 8:15 pm
Posts: 5
During the Aug 11 RAB meeting we discussed the purpose of the dateFormat attribute. It will be used in the same way as the it is used in other ANDS date elements: to specify the date encoding.

The attribute is required in the schema, but isn't shown in the examples.

Also, the current content provider's guide suggests that RDA accepts two types of date encoding:


I think that UTC is a timezone, not a date encoding, and the actual intent is that "UTC" indicate one of the following:

It would be good to get clarification of this in the Content Provider's Guide.

Nigel


Thu Aug 11, 2011 4:52 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 2 posts ] 

All times are UTC + 10 hours [ DST ]


Who is online

Users browsing this forum: No registered users and 1 guest


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group
Designed by ST Software for PTF.