Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > name@type="primary" > namePart
dc > title
collection > record > datafield@tag="245" > subfield@code="a"
Information: Represented by two underlying fields:
dc:type.rdf:PlainLiteral dc:type.skos:prefLabel
Mappings:
RIF-CS:
DC:
MARC-XML:
collection@type
dc > type
collection > record > datafield@tag="655" > subfield@code="a"
History:
r635: Added 'rdf:PlainLiteral' subfield to make the field functional as a JSON Object.
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection@dateAccessioned
dc > date
collection > record > datafield@tag="260" > subfield@code="c"
Also forms the first 6 characters of 008 field as 'YYMMDD':
collection > record > controlfield@tag="008"
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection@dateModified
Unmapped
Unmapped
Represented by two underlying fields:
dc:language.dc:identifier dc:language.skos:prefLabel
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Used on all tags as @xml:lang. Currently hardcoded to 'en' until issue #30 is addressed.
dc > language (truncated URI)
Under collection > record > datafield@tag="041" we have the subfields:
subfield@code="a" (truncated URI)
subfield@code="b" = "iso639-2b"
Finally, we also use the truncated URI in the 008 field:
collection > record > controlfield@tag="008"
History:
r605: Added 'dc:identifier' subfield.
Represented by two underlying fields:
dc:coverage.vivo:DateTimeInterval.vivo:start dc:coverage.vivo:DateTimeInterval.vivo:end
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > coverage > temporal > date@type="dateFrom"
collection > coverage > temporal > date@type="dateTo"
Unmapped
Unmapped
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > coverage > temporal > text
dc > subject
collection > record > datafield@tag="653" > subfield@code="a"
History:
r605: Field name changed to be more semantic web ready.
Represented by five underlying fields:
dc:coverage.vivo:GeographicLocation.0.dc:type dc:coverage.vivo:GeographicLocation.0.gn:name dc:coverage.vivo:GeographicLocation.0.geo:long dc:coverage.vivo:GeographicLocation.0.geo:lat dc:coverage.vivo:GeographicLocation.0.dc:identifier dc:coverage.vivo:GeographicLocation.0.redbox:wktRaw
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Everything is mapped under: collection > coverage > spatial
There are two scenarios:
1) When 'dc:type' is 'free' then build a DCMI Point as: spatial@type="dcmiPoint"
with a template like: 'name=${gn:name}; east=${geo:long}; north=${geo:lat};'
2) Otherwise dc:type will go into spatial@type and gn:name will be used as the text value of spatial.
Unmapped
Unmapped
History:
r605: Subfields changed to use VIVO terminology, and top level field changed to be more semantic web ready.
Represented by three underlying fields:
dc:description:0:text dc:description:0:type dc:description:0:shadow
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Uses 'shadow' in: collection > description@type=full/brief/note
dc > description
collection > record > datafield@tag="520" > subfield@code="a"
Represented by three underlying fields:
dc:relation.swrc:Publication.0.dc:identifier dc:relation.swrc:Publication.0.dc:title dc:relation.swrc:Publication.0.skos:note
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > relatedInfo@type="publication" > identifier@type="url"
dc > relation
collection > record > datafield@tag="856" > subfield@code="u"
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > relatedInfo@type="website" > identifier@type="url"
dc > relation
collection > record > datafield@tag="856" > subfield@code="u"
History:
Represented by seven underlying fields:
dc:relation.vivo:Dataset.0.dc:identifier dc:relation.vivo:Dataset.0.vivo:Relationship.rdf:PlainLiteral dc:relation.vivo:Dataset.0.vivo:Relationship.skos:prefLabel dc:relation.vivo:Dataset.0.dc:identifier dc:relation.vivo:Dataset.0.skos:note dc:relation.vivo:Dataset.0.redbox:origin dc:relation.vivo:Dataset.0.redbox:publish
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped... could use relatedObject( issue #31 )
dc > relation
collection > record > datafield@tag="856" > subfield@code="u"
History:
Represented by underlying fields:
dc:creator.foaf:Person.0.dc:identifier dc:creator.foaf:Person.0.foaf:name dc:creator.foaf:Person.0.foaf:title dc:creator.foaf:Person.0.redbox:isCoPrimaryInvestigator dc:creator.foaf:Person.0.redbox:isPrimaryInvestigator dc:creator.foaf:Person.0.foaf:givenName dc:creator.foaf:Person.0.foaf:familyName dc:creator.foaf:Person.0.foaf.Organization.dc:identifier dc:creator.foaf:Person.0.foaf.Organization.skos:prefLabel identifierText.0.creatorName.input
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Because Mint sends its own Parties (EAC-CPF) records to the NLA, we just need to link by identifier:
collection > relatedObject > key with the static addition of:
collection > relatedObject > relation@type="hasCollector"
dc > creator (full names, see issue #11 though)
The first creator is mapped to:
collection > record > datafield@tag="100" > subfield@code="a"
Additional creators are mapped to:
collection > record > datafield@tag="700" > subfield@code="a"
Proposal for Future Work: This field should become 'dc:creator.foaf:Agent' at the top level, with a new sub-field of 'dc:type' which can contain values like 'foaf:Person' or 'foaf:Organisation' to accommodate institutional authors.
There was some discussion around this, and the idea of using a value in 'dc:type' was not an ontology based decision, but one driven by the simplicity of designing templates and algorithms when mapping metadata.
History:
r605: Some subfields changed to be more semantic web ready, 'dc:title' has been replaced with 'foaf:name' and 'foaf:title'.
Represented by six underlying fields:
locrel:prc.foaf:Person.dc:identifier locrel:prc.foaf:Person.foaf:name locrel:prc.foaf:Person.foaf:title locrel:prc.foaf:Person.foaf:givenName locrel:prc.foaf:Person.foaf:familyName locrel:prc.foaf:Person.foaf:email pcName.identifierText
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Because Mint sends its own Parties records to NLA, we just need to link by identifier:
collection > relatedObject > key with the static addition of:
collection > relatedObject > relation@type="isPrimaryContactFor"
Unmapped
Unmapped
History:
r605: Field names changed to be more semantic web ready, 'dc:title' has been replaced with 'foaf:name' and 'foaf:title'.
Represented by five underlying fields:
swrc:supervisor.foaf:Person.0.dc:identifier swrc:supervisor.foaf:Person.0.foaf:name swrc:supervisor.foaf:Person.0.foaf:title swrc:supervisor.foaf:Person.0.foaf:givenName swrc:supervisor.foaf:Person.0.foaf:familyName identifierText.0.supName.input
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
collection > record > datafield@tag="720" > subfield@code="a"
History:
r605: Field names changed to be more semantic web ready, 'dc:title' has been replaced with 'foaf:name' and 'foaf:title'.
Free text input captured in(but these are not used for mapping):
identifierText.0.collaborativeName.input
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
r605: Field name changed to be more semantic web ready.
Represented by two underlying fields:
dc:subject.anzsrc:for.0.rdf:resource dc:subject.anzsrc:for.0.skos:prefLabel
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Only the actually code is sent to ANDS, not the label:
collection > subject@type="anzsrc-for". The termIdentifier could also be provided here ( issue #108 )
The labels only are mapped to 'dc:subject'
Both the code and label are mapped to here:
collection > record > datafield@tag="654" > subfield@code="a"
And the static string 'ANZSRC-FOR' is mapped here:
collection > record > datafield@tag="654" > subfield@code="2"
Mappings:
RIF-CS:
DC:
MARC-XML:
Only the actually code is sent to ANDS, not the label:
collection > subject@type="anzsrc-seo". The termIdentifier could also be provided here ( issue #108 )
The labels only are mapped to 'dc:subject'
Both the code and label are mapped to here:
collection > record > datafield@tag="654" > subfield@code="a"
And the static string 'ANZSRC-SEO' is mapped here:
collection > record > datafield@tag="654" > subfield@code="2"
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > subject@type="local"
dc > subject
collection > record > datafield@tag="653" > subfield@code="a"
History:
r605: Field name changed to be more semantic web ready.
Represented by two underlying fields:
dc:subject.anzsrc:toa.rdf:resource dc:subject.anzsrc:toa.skos:prefLabel
Information:
Purpose / Notes
Internal Usage
ReDBox Forms
The ANZSRC 'Type of Research Activity' for this research project.
None
Optional. Labeled as 'Type of Research Activity'. This is implemented as a select control populated by a static list held locally in ReDBox.
Mappings:
RIF-CS:
DC:
MARC-XML:
Only the actually code is sent to ANDS, not the label:
collection > subject@type="anzsrc-toa"
Unmapped
Unmapped
History:
r605: Field names changed to be more semantic web ready.
Represented by four underlying fields:
dc:accessRights.skos:prefLabel dc:accessRights.dc:identifier dc:accessRights.dc:RightsStatement.skos:prefLabel dc:accessRights.dc:RightsStatement.dc:identifier dc:accessRightsType
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > rights > accessRights (dc:accessRights.skos:prefLabel) and collection > rights > accessRights@rightsType@rightsURI (dc:accessRights.dc:identifier)
collection > rights > rightsStatement (dc:accessRights.dc:RightsStatement.skos:prefLabel) and collection > rights > rightsStatement@rightsURI(dc:accessRights.dc:RightsStatement.dc:identifier)
Not mapped
Not mapped
Mappings:
RIF-CS:
DC:
MARC-XML:
Only the license names are sent to ANDS:
collection > rights > licence (dc:license.skos:prefLabel) and collection > rights > licence@rightsUri (dc:license.dc:identifier)
dc > rights (only the URLs)
collection > record > datafield@tag="540" > subfield@code="a" (only the URLs)
Thought for future work Mint could provide an authority for licences.
History:
r605: Field names changed to be more semantic web ready.
Represented by four underlying fields:
dc:identifier.rdf:PlainLiteral dc:identifier.dc:type.rdf:PlainLiteral dc:identifier.dc:type.skos.prefLabel dc:identifier.redbox:origin
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > identifier@type="..." (the type and identifier)
dc:identifier
collection > record > controlfield@tag="001"
History:
r535: Fields spun off to stand alone, to clarify the 'vivo:Location' field below.
History:
r635: Added 'rdf:PlainLiteral' subfield to both the identifier and the type to make the field functional as a JSON Object.
Represented by underlying fields:
dc:additionalidentifier.rdf:PlainLiteral dc:additionalidentifier.dc:type.rdf:PlainLiteral dc:additionalidentifier.dc:type.skos.prefLabel
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > identifier@type="..." (the type and identifier)>name@type="primary">namePart
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > location > address > electronic@type="url"
Unmapped
Unmapped
History:
Represented by two underlying fields:
vivo:Location.vivo:GeographicLocation.gn:name vivo:Location.vivo:GeographicLocation.skos:note
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > location > address > physical > addressPart@type="text"
Unmapped
Unmapped
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
r605: Field name changed to be more semantic web ready.
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
r605: Field name changed to be more semantic web ready.
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
r605: Field name changed to be more semantic web ready.
Represented by two underlying fields:
foaf:Organization.dc:identifier foaf:Organization.skos:prefLabel
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Because Mint sends its own Parties records to ANDS, we just need to link by identifier:
collection > relatedObject > key with the static addition of:
collection > relatedObject > relation@type="isManagedBy"
dc > contributor
collection > record > datafield@tag="710" > subfield@code="b"
The template also maps your institution (by default 'Uni. of Newcastle') to:
collection > record > datafield@tag="710" > subfield@code="a"
History:
r605: Field names changed to be more semantic web ready.
Represented by two underlying fields:
foaf:fundedBy.foaf:Agent.0.dc:identifier foaf:fundedBy.foaf:Agent.0.skos:prefLabel
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
r605: Field names changed to be more semantic web ready.
Represented by four underlying fields:
foaf:fundedBy.vivo:Grant.0.redbox:internalGrant foaf:fundedBy.vivo:Grant.0.redbox:grantNumber foaf:fundedBy.vivo:Grant.0.dc:identifier foaf:fundedBy.vivo:Grant.0.skos:prefLabel
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Because Mint sends its own Activity records to ANDS, we just need to link by identifier/key:
collection > relatedObject > key with the static addition of:
collection > relatedObject > relation@type="isOutputOf"
Unmapped
Unmapped
History:
r605: Field names changed to be more semantic web ready.
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
r605: Field name changed to be more semantic web ready.
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Future thought Could be managed through Mint.
History:
r605: Field name changed to be more semantic web ready.
Represented by two underlying fields:
redbox:ManagementPlan.redbox:hasPlan redbox:ManagementPlan.skos:note
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Future thought Could link to an attachment or Mint record.
History:
r605: Field names changed to be more semantic web ready.
Represented by three underlying fields:
skos:note.0.dc:created skos:note.0.foaf:name skos:note.0.dc:description
Information:
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
History:
Represented by eight underlying fields:
redbox:submissionProcess.redbox:submitted redbox:submissionProcess.dc:date redbox:submissionProcess.dc:description redbox:submissionProcess.locrel:prc.foaf:Person.foaf:name redbox:submissionProcess.locrel:prc.foaf:Person.foaf:phone redbox:submissionProcess.locrel:prc.foaf:Person.foaf:mbox redbox:submissionProcess.dc:title redbox:submissionProcess.skos:note
Information:
Purpose / Notes
Internal Usage
ReDBox Forms
Provides read-only access to submission data that comes from self-submission processes. eg. An academic submitting their data for ingest via the web portal.
None
This tab is all read-only, and simply displays the data for informational purposes to administrative staff.
Mappings:
RIF-CS:
DC:
MARC-XML:
Unmapped
Unmapped
Unmapped
Purpose / Notes
Internal Usage
ReDBox Forms
Corresponds to system-config rifcs key: "recordAsLocation", which picks whether to show the record as a rifcs location, and if so, the template to use (usually the record URL pattern).
None
The field exists under Management>Location
Mappings:
RIF-CS:
DC:
MARC-XML:
collection > location > address > electronic@type="url" > value
Unmapped
Unmapped