Navigating Networks Dataset

The sections below detail information about the dataset that is constructed by the RdfExport application for use by the Navigating Networks Service by periodically exporting data from the AusStage relational database.

• Export Steps
• RDF Values & Source Fields
• Contributors
• Contributor Functions
• Contributor Relationships
• Events
• Contributor Functions at Events
• Organisations
• RDF Ontologies
• In Use
• Aus-e-Stage Ontology
• Planned for Use
• AusStage Unique Id Encoding Scheme
• Additional Information

Export Steps

The RdfExport application undertakes the following steps to build the dataset

1. An export of all contributor records
2. An export of contributor functions
3. An export of contributor relationships
4. An export of events and contributor relationships to events
5. An Export of functions that contributors have had when they've contributed to an event

RDF Values & Source Fields

Contributors

SQL Code

SELECT c.contributorid, c.first_name, c.last_name, LOWER(g.gender), nationality, 
       c.yyyydate_of_birth, c.mmdate_of_birth, c.dddate_of_birth 
FROM contributor c, gendermenu g, 
     (SELECT DISTINCT contributorid FROM conevlink WHERE eventid IS NOT NULL) ce 
WHERE c.gender = g.genderid(+) 
AND c.contributorid = ce.contributorid 
ORDER BY contributorid

Contributor Functions

SQL Code

SELECT c.contributorid, cp.preferredterm
FROM contributor c, contributorfunctpreferred cp, contfunctlink cl,
     (SELECT DISTINCT contributorid FROM conevlink WHERE eventid IS NOT NULL) ce
WHERE c.contributorid = cl.contributorid
AND cl.contributorfunctpreferredid = cp.contributorfunctpreferredid
AND c.contributorid = ce.contributorid
ORDER BY contributorid

Contributor Relationships

SQL Code

SELECT c.contributorid, c1.collaboratorid, COUNT(c.contributorid) as collaborations 
FROM conevlink c, (SELECT eventid, contributorid AS collaboratorid FROM conevlink WHERE contributorid IS NOT NULL AND eventid IS NOT NULL) c1 
WHERE c.eventid = c1.eventid 
AND c.contributorid IS NOT NULL 
GROUP BY c.contributorid, c1.collaboratorid 
ORDER BY contributorid

Events

SQL Code

SELECT DISTINCT e.eventid, e.event_name, c.contributorid, 
                e.yyyyfirst_date, e.mmfirst_date, e.ddfirst_date, 
                e.yyyylast_date, e.mmlast_date, e.ddlast_date 
FROM events e, conevlink c  
WHERE e.eventid = c.eventid 
AND e.eventid IS NOT NULL 
AND c.contributorid IS NOT NULL 
ORDER BY e.eventid

Contributor Functions at Events

SQL Code

SELECT cl.contributorid, cl.eventid, cfp.preferredterm 
FROM conevlink cl, contributorfunctpreferred cfp 
WHERE cl.eventid IS NOT NULL 
AND cl.contributorid IS NOT NULL 
AND cl.function = cfp.contributorfunctpreferredid 
ORDER BY contributorid

Organisations

SQL Code

SELECT organisationid, name, other_names1, other_names2, other_names3
FROM organisation

RDF Ontologies

In Use

Aus-e-Stage Ontology

To expedite the construction of the dataset an Aus-e-Stage ontology is used. It is important to note that this ontology does not pre-empt any work conducted under the AusStage phase 4 project. Once the flattening of the AusStage dataset has occurred and the ontologies constructed have been finalised, the ontology used for this dataset should be retired and replaced with the output of the AusStage phase 4 project.

Details of the ontology are available on the AuseStageOntology page.

Planned for Use

AusStage Unique Id Encoding Scheme

To assist in the clarity of AusStage unique identifiers in the dataset the following encoding scheme is used:

• A unique identifier is prefixed with ausstage:
• If the unique identifier is for a contributor c: is then added
• If the unique identifier is for an event e: is then added

The AusStageURI class in the au.edu.ausstage.vocabularies package provides convenience methods for encoding identifiers, and converting identifiers into the persistent URLs used by the AusStage website

The class also provides functionality that encodes a unique identifier for the collaboration objects in the NavigatingNetworksDataset the identifier takes the form:

ausstage:rel:id1-id2

Where id1 and id2 are contributor ids. The URI is resolved to a URL in the Navigating Networks site that can provide additional information about the collaboration relationship.

Additional Information

• http://en.wikipedia.org/wiki/Resource_Description_Framework