This page details the work being undertaken to move ReDBox form fields into closer alignment with common ontologies/vocablaries.
Whilst ReDBox does not make rigorous use of these technologies, the efforts to align our form data is an attempt to provide clarity to the community as well as make downstream conversions easier to metadata outputs such as VIVO.
To clarify the information below it helps to be aware of a few design choices/contraints we operate within:
Jaffa (our Javascript form library) allows lists of fields (eg. a list of creators) to be generated from a template. The template is provided as the ZEROth item of a list, and real data then comes back from the form submission as 1, 2, 3 etc... This is why you will see xxx.0.xxx is field names.
The fullstop character is used in our JSON to represent how we would format a child relationship in XML, so 'dc:coverage.vivo:DateTimeInterval.vivo:start' would end up as something like:
<dc:coverage> <vivo:DateTimeInterval> <vivo:start>XXXX</vivo:start> </vivo:DateTimeInterval> </dc:coverage>
In a perfect world we would be RDF purists and all form fields would contain a predicate leading to a class that contain properties. Sometimes we aren't this strict however, particularly for operational form fields we have no intention of ever exporting. Having said this if some of the shortcuts found herein are too jarring for you, please advise if you have a reasonably succinct alternative that is better. Happy to evolve this design.
We are also using a 'redbox' namespace to cover any fields we couldn't find good alternatives for. For the moment there is no specification for this namespace, and we may never have one if we can phase out its usage.
Please feel free to propose additional namespaces or alternatives we missed that cover things under 'redbox' (including the ANDS-VITRO namespace as soon as it has a home on the web)... although we are trying to stick to significant implementations, not little local yokels.
This is a summary of the complete list with links to each field.