Comet Implementation Status
Current Phase: Local Implementation
Requirements Gathering DONE 
Gathered requirements and user stories from stakeholders at each campus. Comet feature list developed and shared. Evaluated technical platform options against formal criteria; Hyrax selected.
Initial Development DONE
Initial development by Surfliner team guided by feature list. Overall focus on getting Comet ready for local implementation and content migration at each campus.
Local Implementation IN PROGRESS 
Configuration of local instances and start of content migration. Select stakeholders begin to use Comet for managing local digital content and provide feedback. Potential temporary integration with legacy discovery platforms.
Administrative Dashboard & UI
READY
Modern, Accessible User Interface
READY
Our initial interface is based on Hyrax, a general purpose repository toolkit from Samvera. We expect to make theming updates and improvements to UX and Accessibility on an ongoing basis.
Administrative Content Discovery and Access
READY
Content Organization
IN PROGRESS
Complex and Nested Objects
READY
Current interfaces support Objects with many files and component Objects with arbitrarily deep nesting. Object membership relationships are represented using the Portland Common Data Model (PCDM).
Collections
READY
Objects can be organized into collections and may belong to many different collections. Collection membership relationships are represented using the Portland Common Data Model (PCDM).
Semantic Object Relationships
NOT STARTED 
LOCAL REQUIREMENTS NEEDED 
File Management
IN PROGRESS IN PROGRESS / LOCAL REQUIREMENTS NEEDED
Multiple File Types
READY / LOCAL REQUIREMENTS NEEDED
Support for upload, download, and characterization of arbitrary bitstreams is included. As we add more features (like automated derivatives) support for file types will become more complex and need ongoing attention.
Automated Derivative Processing
IN PROGRESS / LOCAL REQUIREMENTS NEEDED
Administrative Files
IN PROGRESS / LOCAL REQUIREMENTS NEEDED
Persistence and Preservation Support
IN PROGRESS
Unique Identification (ARKs)
READY
ARKs are managed via integration to EZID.
File Characterization
READY
Files are characterized on upload using the File Information Tool Set (FITS).
Provenance Events and Audit Log
NOT STARTED / LOCAL REQUIREMENT NEEDED
Our implementation does some minimal audit logging for Object lifecycles, but we haven’t validated this against local requirements and don’t consider it a complete provenance model or feature set.
File Fixity Audit
NOT STARTED
Metadata Management
IN PROGRESS
Configurable Metadata Schemas
READY
Metadata is configurable from the community-driven M3 standard file format. Configurable metadata drives integration with discovery systems.
Object, File, and Collection Metadata Forms
IN PROGRESS
Object and Collection forms exist
Metadata Versioning
NOT STARTED
Metadata Validation
IN PROGRESS
Minimal validation of presence for required fields is provided. Other validation requirements are being identified
Content Lifecycle
IN PROGRESS
Multi-Step Workflows
READY
Comet supports a highly configurable workflow engine
Content Publish
IN PROGRESS
We’ve trialed content publish to a front-end application (an OAI-PMH metadata harvest endpoint) and a content delivery protocol (IIIF), but
we expect continued technical challenges as we roll out support for other endpoints. We consider the current UI for content publish
experimental.
Tombstones
NOT STARTED
Projects
READY
Bulk Import/Export
IN PROGRESS
Implementing the Bulkrax engine for import/export
Bulk Object Import
IN PROGRESS
Export
NOT STARTED
Bulk Metadata Export
NOT STARTED
Batch Metadata Overlay
NOT STARTED
Customizable Exports
NOT STARTED
Access Controls
IN PROGRESS
User and Group-Based Access Controls
READY
The basic Access Control model for Comet and across integrated discovery and delivery systems is in place.
Role Management
IN PROGRESS
The access control model and its implementation is documented here.
Basic role management is in place for admins, but better management is needed for per-Project role assignments. We’re engaged in community discussions around this feature set.
Visibility States
IN PROGRESS / LOCAL REQUIREMENT NEEDED
Contractual Control
IN PROGRESS / LOCAL REQUIREMENT NEEDED
Embargo and lease management is in active development. Local requirements are needed for license-driven access control, culturally sensitive materials, and other specialized policy needs.
Analytics and Reporting
NOT STARTED / LOCAL REQUIREMENT NEEDED
Usage Metrics
NOT STARTED
Content Reports
NOT STARTED