dc:titleInformation:
Mappings:
dc:typeInformation: Represented by two underlying fields: dc:type.rdf:PlainLiteral dc:type.skos:prefLabel
Mappings:
History:
dc:createdInformation:
Mappings:
dc:modifiedInformation:
Mappings:
dc:languageRepresented by two underlying fields: dc:language.dc:identifier dc:language.skos:prefLabel Information:
Mappings:
History:
dc:coverage.vivo:DateTimeIntervalRepresented by two underlying fields: dc:coverage.vivo:DateTimeInterval.vivo:start dc:coverage.vivo:DateTimeInterval.vivo:end Information:
Mappings:
History:
dc:coverage.redbox:timePeriodInformation:
Mappings:
History:
dc:coverage.vivo:GeographicLocationRepresented 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:
History:
dc:descriptionRepresented by three underlying fields: dc:description:0:text dc:description:0:type dc:description:0:shadow Information:
Mappings:
|
| Purpose / Notes | A list of links to any published material related to this collection. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. A simple UI allowing three free-text fields, one for the URL, one for title, and another for notes (which are not mapped anywhere). |
| Checked | v1.5 |
Mappings:
| RIF-CS: | collection > [email protected]="publication" > [email protected]="url" |
| DC: | dc > relation |
| MARC-XML: | collection > record > [email protected]="856" > [email protected]="u" |
History:
dc:relation.bibo:Website
Represented by three underlying fields:
dc:relation.bibo:Website.0.dc:identifier dc:relation.bibo:Website.0.dc:title dc:relation.bibo:Website.0.skos:note
Information:
| Purpose / Notes | A list of links to any websites related to this collection. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. A simple UI allowing three free-text fields, one for the URL, one for title, and another for notes (which are not mapped anywhere). |
| Checked | v1.5 |
Mappings:
| RIF-CS: | collection > [email protected]="website" > [email protected]="url" |
| DC: | dc > relation |
| MARC-XML: | collection > record > [email protected]="856" > [email protected]="u" |
History:
dc:relation.vivo:Dataset
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:
| Purpose / Notes | A list of links to any data related to this collection. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. This is a complicated field provisioning a linked data relationship to other ReDBox datasets. Future work may involve a more global lookup against RDA |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped... could use relatedObject( issue #31 ) |
| DC: | dc > relation |
| MARC-XML: | collection > record > [email protected]="856" > [email protected]="u" |
History:
- r605: Major overhaul of form functionality for linked data usage.
- r605: Field name changed to be more semantic web ready.
- r535: 'dc:title' subfield added.
dc:creator.foaf:Person
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:
| Purpose / Notes | This field holds a list of the creators of the work, and their association affiliations (eg. Faculty of XYZ) |
|---|---|
| Internal Usage | This is a faceted field, on 'foaf:name'. |
| ReDBox Forms | Mandatory. Labeled as 'Creators'. The UI here is one of the more complicated areas of the form. Free-text entries are possible, although they are typically used to fuel a search of Mint, which will return authoritative data to each field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | 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 > [email protected]="hasCollector" |
| DC: | dc > creator (full names, see issue #11 though) |
| MARC-XML: | The first creator is mapped to: collection > record > [email protected]="100" > [email protected]="a" Additional creators are mapped to: collection > record > [email protected]="700" > [email protected]="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'.
locrel:prc.foaf:Person
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:
| Purpose / Notes | The primary contact person for the collection. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Primary Contact', and also backed into a lookup against Mint, similar to creator, although less detailed. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | 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 > [email protected]="isPrimaryContactFor" |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready, 'dc:title' has been replaced with 'foaf:name' and 'foaf:title'.
swrc:supervisor.foaf:Person
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:
| Purpose / Notes | A list of supervisors associated with the data creation. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Supervisors', and also backed into a lookup against Mint, similar to creator, although less detailed. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | collection > record > [email protected]="720" > [email protected]="a" |
History:
- r605: Field names changed to be more semantic web ready, 'dc:title' has been replaced with 'foaf:name' and 'foaf:title'.
dc:contributor.locrel:clb.0.foaf:Agent
Free text input captured in(but these are not used for mapping):
identifierText.0.collaborativeName.input
Information:
| Purpose / Notes | List the names of any other collaborators on the research project (both people and organizations). |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Collaborators' and implemented as a basic list of free-text entry fields. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
dc:subject.anzsrc:for
Represented by two underlying fields:
dc:subject.anzsrc:for.0.rdf:resource dc:subject.anzsrc:for.0.skos:prefLabel
Information:
| Purpose / Notes | A List of ANZSRC codes for 'Field of Research' that the research project is associated with. |
|---|---|
| Internal Usage | This is a faceted field, grouped with keywords. |
| ReDBox Forms | Optional. Labeled as 'Fields of Research'. This is implemented as a select control populated by a lookup against Mint. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Only the actually code is sent to ANDS, not the label: collection > [email protected]="anzsrc-for". The termIdentifier could also be provided here ( issue #108 ) |
| DC: | The labels only are mapped to 'dc:subject' |
| MARC-XML: | Both the code and label are mapped to here: collection > record > [email protected]="654" > [email protected]="a" And the static string 'ANZSRC-FOR' is mapped here: collection > record > [email protected]="654" > [email protected]="2" |
History:
dc:subject.anzsrc:seo
Represented by two underlying fields:
dc:subject.anzsrc:seo.0.rdf:resource dc:subject.anzsrc:seo.0.skos:prefLabel
Information:
| Purpose / Notes | A List of ANZSRC codes for 'Socio-Economic Objective' that the research project is associated with. |
|---|---|
| Internal Usage | This is a faceted field, grouped with keywords. |
| ReDBox Forms | Optional. Labeled as 'Socio-Economic Objective'. This is implemented as a select control populated by a lookup against Mint. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Only the actually code is sent to ANDS, not the label: collection > [email protected]="anzsrc-seo". The termIdentifier could also be provided here ( issue #108 ) |
| DC: | The labels only are mapped to 'dc:subject' |
| MARC-XML: | Both the code and label are mapped to here: collection > record > [email protected]="654" > [email protected]="a" And the static string 'ANZSRC-SEO' is mapped here: collection > record > [email protected]="654" > [email protected]="2" |
History:
dc:subject.vivo:keyword.0.rdf:PlainLiteral
Information:
| Purpose / Notes | A list of user entered keywords covering the research project's subject area. |
|---|---|
| Internal Usage | This is a faceted field, grouped with ANZSRC codes. |
| ReDBox Forms | Mandatory (at least one). Labeled as 'Keywords' and implemented as a free-text entry field. An autocomplete feature will try to suggest already existing keywords as you type. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | collection > [email protected]="local" |
| DC: | dc > subject |
| MARC-XML: | collection > record > [email protected]="653" > [email protected]="a" |
History:
- r605: Field name changed to be more semantic web ready.
dc:subject.anzsrc:toa
Represented by two underlying fields:
dc:subject.anzsrc:toa.rdf:resource dc:subject.anzsrc:toa.skos:prefLabel
Information:
| Purpose / Notes | The ANZSRC 'Type of Research Activity' for this research project. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | 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: | Only the actually code is sent to ANDS, not the label: collection > [email protected]="anzsrc-toa" |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready.
dc:accessRights
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:
| Purpose / Notes | These fields indicate any and all rights held over the data. Within the "Access Rights/Conditions" section the 'dc:accessRights.skos:prefLabel' is for the access rights text, whilst the 'dc:accessRights.dc:identifier' contains a URI for the linked access rights information. Within the "Rights" section, 'dc:accessRights.dc:RightsStatement.skos:prefLabel' is used for the rights text and 'dc:accessRights.dc:RightsStatement.dc:identifier' as a link to a rights statement (resource). Type indicates the access rights type. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Labeled as 'Access/Rights' and implemented as free-text entry fields. Mandatory; at least one of the field sets (Access Rights or Rights) must be populated, but both are allowed. The type 'open' is selected on selection of an open licence. |
| Checked | v1.9 |
Mappings:
| RIF-CS: | collection > rights > accessRights (dc:accessRights.skos:prefLabel) and collection > rights > [email protected]@rightsURI (dc:accessRights.dc:identifier) collection > rights > rightsStatement (dc:accessRights.dc:RightsStatement.skos:prefLabel) and collection > rights > [email protected](dc:accessRights.dc:RightsStatement.dc:identifier) |
| DC: | Not mapped |
| MARC-XML: | Not mapped |
History:
- r605: Field names changed to be more semantic web ready.
- r552: Issue #4 fixed addressing subtle changes to mappings.
dc:license
Represented by two underlying fields:
dc:license.skos:prefLabel dc:license.dc:identifier
Information:
| Purpose / Notes | Specifies what license(s) the data is released under. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled 'License - ...'. At present the creative commons licenses are implemented as a select control populated from a data list held in ReDBox. The idea is that implementers will add to the list of possibilities as they will manage a set of licences. The older version of ReDBox provided a text box for free text entry but it is hoped that the linking model encourages the implementation of licence management. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Only the license names are sent to ANDS: collection > rights > licence (dc:license.skos:prefLabel) and collection > rights > [email protected] (dc:license.dc:identifier) |
| DC: | dc > rights (only the URLs) |
| MARC-XML: | collection > record > [email protected]="540" > [email protected]="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.
dc:identifier
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:
| Purpose / Notes | Specifies the unique identifier in use for this record. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Mandatory. Labeled as 'Identifier'. 'redbox:origin' is a checkbox that allows the user to delegate this task to the system. It is checked by default. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | collection > [email protected]="..." (the type and identifier) |
| DC: | dc:identifier |
| MARC-XML: | collection > record > [email protected]="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.
dc:additionalidentifier
Represented by underlying fields:
dc:additionalidentifier.rdf:PlainLiteral dc:additionalidentifier.dc:type.rdf:PlainLiteral dc:additionalidentifier.dc:type.skos.prefLabel
Information:
| Purpose / Notes | Specifies additional identifiers in use for this record. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Identifier'. |
| Checked | v1.9 |
Mappings:
| RIF-CS: | collection > [email protected]="..." (the type and identifier)>[email protected]="primary">namePart |
| DC: | |
| MARC-XML: |
bibo:Website.0.dc:identifier
Information:
| Purpose / Notes | Any URLs where the research data can be found. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Mandatory (sometimes). Within the Location section, either this field, or physical storage will be required. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | collection > location > address > [email protected]="url" |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r635: Altered base field from 'vivo:Location' to 'bibo:Website' to make the field functional as a JSON Object.
- r605: Field name changed to be more semantic web ready.
- r535: Identifier removed to become its own field (see 'dc:identifier' above), and 'url' has become a list.
vivo:Location
Represented by two underlying fields:
vivo:Location.vivo:GeographicLocation.gn:name vivo:Location.vivo:GeographicLocation.skos:note
Information:
| Purpose / Notes | These fields describe the physical location of the underlying data. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Mandatory (sometimes). Within the Location section, either this field, or URL(s) will be required. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | collection > location > address > physical > [email protected]="text" |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready.
redbox:retentionPeriod
Information:
| Purpose / Notes | Period of time that the data must be kept in line with institutional/funding body retention policies. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Mandatory. Labeled as 'Retention Period'. Free-text entry field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
dc:extent
Information:
| Purpose / Notes | Description of the extent of material, such as number of files or physical items. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Mandatory. Labeled as 'Extent or Quantity', and implemented as a free-text entry field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
redbox:disposalDate
Information:
| Purpose / Notes | The date this data can be disposed of. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Disposal Date' and implemented as a calendar control allowed granularity down to the day. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
locrel:own.foaf:Agent.0.foaf:name
Information:
| Purpose / Notes | A list of the names of Intellectual Property owners of this data (can be people or organizations). |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Data Owner (IP)', and implemented as a list of free-text entry fields. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
locrel:dtm.foaf:Agent.foaf.name
Information:
| Purpose / Notes | Person/institution identified as custodian of the data. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Data Custodian', and implemented as a basic free-text field |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
foaf:Organization
Represented by two underlying fields:
foaf:Organization.dc:identifier foaf:Organization.skos:prefLabel
Information:
| Purpose / Notes | The organizational unit (ie. internal to your organization) affiliated with this research project. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Data Affiliation', and implemented as a select control populated by a look against Mint 'Groups'. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | 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 > [email protected]="isManagedBy" |
| DC: | dc > contributor |
| MARC-XML: | collection > record > [email protected]="710" > [email protected]="b" The template also maps your institution (by default 'Uni. of Newcastle') to: collection > record > [email protected]="710" > [email protected]="a" |
History:
- r605: Field names changed to be more semantic web ready.
foaf:fundedBy.foaf:Agent
Represented by two underlying fields:
foaf:fundedBy.foaf:Agent.0.dc:identifier foaf:fundedBy.foaf:Agent.0.skos:prefLabel
Information:
| Purpose / Notes | A list of funding bodies for the research project funding. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Funding Body/s', and implemented as free-text entry fields with autocomplete lookups against Mint to retrieve identifiers. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready.
foaf:fundedBy.vivo:Grant
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:
| Purpose / Notes | Links the collection to a list of research projects (grants, or 'Activities' in Mint/ANDS terms). |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Grant Numbers'. Implementation is a little complicated. If the grant is flagged as internal then simple free-text entry of the grant number and label is expected. Otherwise the label field will be locked and typing anything in the grant number field will perform an autocomplete lookup against Mint (for both numbers and/or labels) and will populate the grant number, label and identifier upon selection. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | 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 > [email protected]="isOutputOf" |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready.
swrc:ResearchProject.dc:title
Information:
| Purpose / Notes | The title of the research project. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Project Title' and implement as a basic free-text field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
locrel:dpt.foaf:Person.foaf:name
Information:
| Purpose / Notes | The name of the depositor. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Depositor' and implement as a basic free-text field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
dc:SizeOrDuration
Information:
| Purpose / Notes | Intended specifically for the size of electronic data on disk. Used organizationally for scoping storage requirements. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Data Size' and implement as a basic free-text field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field name changed to be more semantic web ready.
dc:Policy
Information:
| Purpose / Notes | A description of an any institutional policies associated with this data. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Institutional Data Management Policy' and implement as a basic free-text field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
Future thought Could be managed through Mint.
History:
- r605: Field name changed to be more semantic web ready.
redbox:ManagementPlan
Represented by two underlying fields:
redbox:ManagementPlan.redbox:hasPlan redbox:ManagementPlan.skos:note
Information:
| Purpose / Notes | Used to indicate whether a data management plan exists for this data. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Data Management Plan'. 'redbox:hasPlan' is a simple 'yes/no' radio control, and notes is a basic free-text field. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
Future thought Could link to an attachment or Mint record.
History:
- r605: Field names changed to be more semantic web ready.
skos:note
Represented by three underlying fields:
skos:note.0.dc:created skos:note.0.foaf:name skos:note.0.dc:description
Information:
| Purpose / Notes | Administrative notes for the record. Issue #20 outlines some required work regarding deletion of notes. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | Optional. Labeled as 'Notes' on its own tab. Description is the only input required, as the time of creation and the logged in user will be used to fill the other fields automatically. |
| Checked | v1.5 |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready.
- r539: Behavioural changes to form for clarity and usability.
redbox:submissionProcess
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 | 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. |
|---|---|
| Internal Usage | None |
| ReDBox Forms | This tab is all read-only, and simply displays the data for informational purposes to administrative staff. |
Mappings:
| RIF-CS: | Unmapped |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
History:
- r605: Field names changed to be more semantic web ready.
redboxAsLocationDefault
Information:
| Purpose / Notes | 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). |
|---|---|
| Internal Usage | None |
| ReDBox Forms | The field exists under Management>Location |
Mappings:
| RIF-CS: | collection > location > address > [email protected]="url" > value |
| DC: | Unmapped |
| MARC-XML: | Unmapped |
