View unanswered posts | View active topics It is currently Wed Aug 15, 2018 9:54 am

All times are UTC + 10 hours [ DST ]




Reply to topic  [ 1 post ] 
Add new Rights element to RIF-CS Schema 
Author Message
ANDS Staff
User avatar

Joined: Thu Feb 10, 2011 11:18 am
Posts: 76
Suggested schema change
Add new rights elements to record Creative Commons licences and other rights information.

Problem this suggestion addresses

At present rights information can be provided only as a type in the description element.
A new rights element will:
• expose rights information at the top level in Research Data Australia
• allow description of Creative Commons licences and display of associated logos in Research Data Australia
• support search filtering by licence type as a guide to re-use potential
• enable machine searching by Creative Commons status
The proposed new elements separate rights, licensing and access information.
However, to permit mapping from and to other schemas where this separation does not exist, all child elements of the rights element can be concatenated into a single element that equates to DCterms:RightsStatement if required.
All elements are optional and repeatable for maximum flexibility of mapping incoming metadata.
Refer to attached document for Right element description and mapping

Identified by

ANDS Staff, ANDS Business Solutions Working Group, various partner suggestions

RIF-CS schema components affected
Existing description element, type="rights" and type="accessRights" for collection records. Not required for services, activities or parties.

Impact on content providers
The intention is to deprecate use of Description of type="rights" and type="accessRights", so that existing content need not be changed but any new content would take advantage of the additional capability.
However, as these types align with new elements, some processing on ingest to ANDS could possibly transform incoming data.
No change to the services accessPolicy element is planned—this will continue to store machine-readable access information for web services only.

Pros
• New element will allow creative commons licences to be specified directly
• New element will provide structured rights information to support searching

Cons
Where existing rights information is included as part of a brief or full description that information could only move into the new structure if changes were made at the data source.

Technical options

Option #1
Introduction of rights wrapper element for accessRights, licence and rightsStatement elements
    <xsd:element name="rights" type="rightsType" minOccurs="0" maxOccurs="1">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">Rights(s) relevant to the collection. </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:complexType name="rightsType">
      <xsd:choice minOccurs="1" maxOccurs="unbounded">
        <xsd:element name="rightsStatement" type="rightsStatementType" minOccurs="0" maxOccurs="unbounded"/>
        <xsd:element name="licence" type="rightsInfoType" minOccurs="0" maxOccurs="unbounded"/>
        <xsd:element name="accessRights" type="rightsInfoType" minOccurs="0" maxOccurs="unbounded"/>

      </xsd:choice>

    </xsd:complexType>
    <xsd:complexType name="rightsInfoType">
      <xsd:sequence>
        <xsd:element name="value" type="xsd:string" minOccurs="0" maxOccurs="1"/>
        <xsd:element name="uri" type="xsd:string" minOccurs="0" maxOccurs="1"/>
      </xsd:sequence>
      <xsd:attribute name="type" use="optional" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>A value taken from a controlled vocabulary indicating the type of rights or licence.</xsd:documentation>
        </xsd:annotation>
      </xsd:attribute>
    </xsd:complexType>
    <xsd:complexType name="rightsStatementType">
      <xsd:sequence>
        <xsd:element name="value" type="xsd:string" minOccurs="0" maxOccurs="1"/>
        <xsd:element name="uri" type="xsd:string" minOccurs="0" maxOccurs="1"/>

      </xsd:sequence>
    </xsd:complexType>

Apart from the above schema additions, changes would be needed for client feeds and for “Publish My Data” input screens and the Java api.
Controlled vocabularies for the “licence” and “accessRights” element types will need to be created.
ANDS will not make transformations at times of harvest, as we do not change the rif-cs received from data sources.
Transition will need to be planned and managed.
Changes will be required to the content providers guide.

Option #2
Introduction of new licence element and leave “accessRights” and “rights” as types of collection description.
    <xsd:element name="licence" type=" licenceType" minOccurs="0" maxOccurs="1">
      <xsd:annotation>
        <xsd:documentation xml:lang="en">Rights(s) relevant to the collection. </xsd:documentation>
      </xsd:annotation>
    </xsd:element>
    <xsd:complexType name=" licenceType ">
      <xsd:sequence>
        <xsd:element name="value" type="xsd:string" minOccurs="0" maxOccurs="1"/>
        <xsd:element name="uri" type="xsd:string" minOccurs="0" maxOccurs="1"/>
      </xsd:sequence>
      <xsd:attribute name="type" use="optional" type="xsd:string">
        <xsd:annotation>
          <xsd:documentation>A value taken from a controlled vocabulary indicating the type of licence.</xsd:documentation>
        </xsd:annotation>
      </xsd:attribute>
    </xsd:complexType>

Apart from the above schema additions changes would be required for “Publish My Data” input screens and the Java api.
Controlled vocabularies for the “licence” element type will need to be created.
No transformations or transition issues.
Changes will be required to the content providers guide.

Option #3
Add “ccLicence” to the controlled vocabulary of the description element to enable description of creative common licence.
The vocabulary term “ccLicence” will need to be added to the ORCA registry “tbl_terms” database table.
The vocabs.xml file will need to be amended to add the vocab description type “ccLicence” definition.
The vocabularies.html will need to be regenerated to reflect the addition of the description type “ccLicence”.
Changes will be required to the content providers guide.


Attachments:
File comment: Rights element description and mapping table
RAB Rights element description and mapping.docx [53.79 KiB]
Downloaded 332 times
Tue Jun 28, 2011 1:30 pm
Profile
Display posts from previous:  Sort by  
Reply to topic   [ 1 post ] 

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.