Publishing objects from Nuxeo to Calisphere is handled through a metadata harvesting process. Your Collection Administrator can initiate harvests for collections in Nuxeo that are ready for publication using our "Harvest and Re-Harvest Requests" form (see below).
Main Content File Requirements
Calisphere harvests "service copies" derived from the "main file" uploaded to Nuxeo–these "service copies" are smaller file formats aimed to support web performance. The harvesting process has a filesize limit for individual files, with a current threshold of 10gb per "main file." For details on on file requirements, please see our Creating Objects and Preparing Files pages.
Web accessible files
We are committed to following the updated UC IT Accessibility Policy. To support this, we encourage all contributors to familiarize themselves with the UC Digital Reformatting Guidelines to better understand accessibility considerations for your digital content. These guidelines will soon be updated to align with WCAG 2.1 AA standards.
Security levels for files
Nuxeo is not intended for managing content including clinical or personally identifiable information (PII) whose disclosure would constitute a violation of HIPAA/HITECH, FERPA, or other similar statutes, regulations, or laws. Content containing PII should be redacted or anonymized prior to ingesting or uploading into Nuxeo. Our Nuxeo application use must comply with UC's Electronic Information Security Policy, IS-3. Please see UC's Systemwide Information Security's resource on protection level classification; note that Nuxeo's protection level classification is P2, and all content files stored in Nuxeo must fall within this provision.
Content and Metadata Considerations
When publishing objects from Nuxeo to Calisphere, please also review these resources which summarize a set of overarching considerations with making collections available through the site:
- Supported Scope of Content and Responsible Access Considerations
- Supported Metadata and Inclusive Description Considerations
Defining Collections to Harvest from Nuxeo
Harvesting from Nuxeo into Calisphere works on a collection-by-collection basis. By "collection," we mean a group digital objects which are hosted in the same Project Folder in Nuxeo, and which you’d like to appear together as a set within the Calisphere interface.
Your Collection Administrator can edit or create new entries in our Collection Registry administrative interface (requires login), which we use to run harvests. Each entry in the Collection Registry contains basic information about the collection that will be displayed in Calisphere (such as title and description).
Objects associated with a given Calisphere collection must be organized within one Nuxeo Project Folder. (The Project Folder can, in turn, have nested Project Folders; in this scenario, all of the objects within the nested Project Folders will also be harvested). Please designate one Nuxeo filepath as the harvesting source for a given Calisphere collection.
Conducting a Harvest from Nuxeo to Test Calisphere Environment, QA, and Publication
Contact us, using the form below, to initiate a harvest (or re-harvest) of a collection from Nuxeo to Calisphere. We'll then run a harvest of your collection to a test Calisphere environment, where we can collectively preview and perform quality assurance (QA) on the items. If we identify errors, we'll confer with you on fixing them -- and will re-harvest to the test Calisphere environment to see the updated results.
If everything looks OK in the testing environment, we'll ask for your approval to publish the records in Calisphere.
Bonus Step: Add Custom Filters to your Published Digital Collection
Digital collections on Calisphere are published with two default filter options: Type of Item (e.g., image, text, audio, etc.) and Decade (e.g., 1910s, 1920s). Interested in adding custom filter selections to your collection? Learn more about Defining Custom Filters in Digital Collections...