Comet Sprint 19 (November 16 - November 29, 2022)

Comet Sprint 19

What was the goal of Sprint 19?
The goal for the overall work cycle is to shore up batch work for ingest and extend it to get batch round trip working so that you can do an export of batch metadata in some format, make changes in the exported format file, and then re-import it to do updates.

The team is doing work that is critical for the overall success of large-scale ingest around managing files and relationships between objects. This includes getting “File Edit” ironed out and making it so that you can control a crucial piece of metadata about files which is the file Use/Type (i.e. marking the difference between a production master, an archival master, etc.).

The team is also working on Shoreline and Comet integration. Some of the file management components are prerequisites to Shoreline ingest because the complexity of the objects that need to be ingested as geodata (shapefiles and rasters, etc.) requires a complex structure that must be manageable. Also in support of Shoreline, there has been some work on the Surfliner schema for metadata configuration and some background work on Shoreline itself just to keep up with dependencies that have been updated.

Accomplishments of Sprint 19:

  • Bug: Fixed issue with the search index on the Comet home page which routes through the Backlight platform; we can now focus on more broad searches in the user dashboard and the existing index behavior
  • Bug: Fixed issue with not being able to remove Objects from Collections
  • Object structure management/relationships
    • Added “Remove from this object” button to Actions in the Item display view (note: the component is detached from the Object, but it is not deleted from the repository)
    • When editing and Object, can use the “Relationships tab” to do structural management of an Object
  • Put in upstream work to get the “Edit File Set” functionality to work
    We’re also interested in showing, in the File Set view details, the various files that it has and their uses/types
  • Working to support the Shoreline profile using Comet’s metadata API (Superskunk)
    • If objects are ingested into Comet using the Shoreline metadata profile, they can be exported to Shoreline using the Comet metadata API
  • Continued to work on the batch upload process via the Bulkrax engine. Meeting with the maintainers of Bulkrax engineers to talk about our goals for it
  • Technical work around upgrading to the Geoblacklight 4.0 release. Implications of this upgrade is that there is a major metadata schema shift that is taking place as part of the 4.0 upgrade. Doing this upgrade now in order to target the new schema and reduce duplicate work [note: UCLA will be using parts of the ingest process for Shoreline]
  • Meetings/Discussions (Project team and subject matter experts):
    • Object structure and relationships
    • Item display area and actions we can take to improve structural management from here. We want the ability to see a deep nested representation of object structure here (components several layers deep–think book with many pages)
    • Initial stages of “Visibility model” discussions with various stakeholders. Want to get folks on the same page about how this works in practice; do these need to be configurable between the individual campuses or can we agree on a shared overarching structure?
    • Subgroup working on the Shoreline platform and Comet’s integration with it

What’s next?
A continuation of the work started in this Sprint

GitLab link: