Add Your New Field(s) to the Services Layer
Follow the next set of steps to add your new field(s) to the Services layer:
Add the new field(s) to the appropriate extension schemas (domain or local) in two places within the Services layer, once to alter the underlying Nuxeo document type schema and again to make an equivalent change to the JAXB schema. (JAXB, or Java Architecture for XML Binding, is used to express the contents of the data base as XML, the format in which data is passed between the layers of the CollectionSpace architecture. To learn more, see http://en.wikipedia.org/wiki/JAXB.).
For Nuxeo, you would edit or create this file:
/services/collectionobject/3rdparty/nuxeo-platform-cs-collectionobject/src/main/resources/schemas/collectionobjects_{customname}.xsd
where {customname} may represent a community or domain, such as "naturalhistory" (and hence the file might be named collectionobjects_naturalhistory.xsd), or a museum, such as "pahma", derived from the Internet hostname "pahma.berkeley.edu" (and hence the file might be named collectionobjects_pahma.xsd)
For JAXB, you would edit or create this file:
/services/collectionobject/jaxb/src/main/resources/collectionobjects_{customname}.xsd
If the files do not already exist, create them and include the new field.
Edit the tenant bindings file to reference your new extension schema.
Perform a Services build and deployment to incorporate these changes into the Services layer.
Hi,
In 1.12, the document for adding a field
http://wiki.collectionspace.org/display/DOC/How+to+add+a+field+or+group+of+fields
gives this information about the services layer work:
> Add Your New Field(s) to the Services Layer
>
> Follow the next set of steps to add your new field(s) to the Services layer:
>
> Add the new field(s) to the appropriate extension schemas (domain or local) in two places within the Services layer, once to alter the underlying Nuxeo document type schema and again to make an equivalent change to the JAXB schema. (JAXB, or Java Architecture for XML Binding, is used to express the contents of the data base as XML, the format in which data is passed between the layers of the CollectionSpace architecture. To learn more, see http://en.wikipedia.org/wiki/JAXB.).
> For Nuxeo, you would edit or create this file:
> /services/collectionobject/3rdparty/nuxeo-platform-cs-collectionobject/src/main/resources/schemas/collectionobjects_{customname}.xsd
> where {customname} may represent a community or domain, such as "naturalhistory" (and hence the file might be named collectionobjects_naturalhistory.xsd), or a museum, such as "pahma", derived from the Internet hostname "pahma.berkeley.edu" (and hence the file might be named collectionobjects_pahma.xsd)
>
> For JAXB, you would edit or create this file:
> /services/collectionobject/jaxb/src/main/resources/collectionobjects_{customname}.xsd
> If the files do not already exist, create them and include the new field.
>
> Edit the tenant bindings file to reference your new extension schema.
> Perform a Services build and deployment to incorporate these changes into the Services layer.
It then refers the reader to
http://wiki.collectionspace.org/display/DOC/Adding+a+Custom+Field+to+a+CollectionObject
Is it the case that this latter page is not current? It still talks about editing core-types-contrib.xml. Do we still do that? Jesse's work on 1.12 name authorities for MMI suggests that he is still editing the manifest.mf file, layouts-contrib.xml, and so on.
Thanks,
Chris
