Skip to content

Milestones

List view

  • Goals: * Various updates to work edit form (IN PROGRESS) * Continued progress towards mapping to/from fedora to ensure full-roundtrip of all metadata (IN PROGRESS) * Reserve a PURL (IN PROGRESS) * Updates to item types/subtypes, includes mappings (IN PROGRESS) * Dashboard updates (IN PROGRESS) * Discard draft of a versioned work (rollback to last deposited version) (IN PROGRESS) Stretch goal: * RabbitMQ changes now that it is available in prod (Note: should not be used yet until finalized according to Ops)

    Due by February 12, 2021
  • * Change to how we handle mapping errors to allow users to fix data errors in Argo (DONE) - see sul-dlss/dor-services-app#1817 * Collection show page and the collection list page (i.e. all works in a collection) (DONE) * Add project tags to registered items and collections: "Project : H2" (DONE) * Implement email notifications and address feedback on existing ones (DONE) * Complete collection edit form to include all fields (DONE) * Page breadcrumb navigation (particularly that gets you back to the dashboard) (DONE) * Various updates to work edit form (IN PROGRESS) * Continued progress towards mapping to/from fedora to support versioning (IN PROGRESS ... 4EVAH) * Reserve a PURL (IN PROGRESS) * Updates to item types/subtypes, includes mappings (IN PROGRESS)

    Due by January 29, 2021
  • - Review H1 --> H2 migration analysis and respond to feedback (DONE) - Review hotwire, re: form validation, to see if it an improvement (DONE) - Review rabbitMQ for message queues (DONE) - Continued progress towards mapping to/from fedora to support versioning (IN PROGRESS) - Implement email notifications and address feedback on existing ones (IN PROGRESS) - Collection show page and the collection list page (i.e. all works in a collection) (IN PROGRESS) - Complete collection form to include all fields (NOT STARTED)

    Due by January 18, 2021
  • # Primary goals: * Update review workflow (mediated deposits) to handle versioning (DONE) * Finish permissions on dashboard (so that reviewers, admins, depositors, etc. see the correct works/collections) (DONE) * Implement automated generation of citation and the ability to select manual/automated (DONE) * Discarding of draft works/collections (DONE) * Implement email notifications (IN PROGRESS) * Continued progress towards mapping to/from fedora to support versioning (IN PROGRESS) * Collection show page and the collection list page (i.e. all works in a collection) (IN PROGRESS) * Complete collection form to include all fields (NOT STARTED) # Stretch goals: * Add type-ahead entry for FAST keyword (OCLC subject terms) (NOT STARTED)

    Due by December 11, 2020
  • # Goals * Ability to version and update an already deposited object (in stage) - note this will require the ability to roundtrip any object in production (DONE) * Continue/complete reviewer workflow changes (CURRENTLY TESTING) * Complete ability to work with draft items and collections (DONE) * Ability to version and update an already deposited collection (in stage) (DONE) * Maps rights and embargo to cocina data model (and see them in Argo as set in H2) (DONE) * Collections created in H2 should be accessioned and visible in Argo (DONE) * Ability to version and update an already deposited collection (in stage) (IN PROGRESS) * Ensure that deposited items belong to the correct H2 related collection in Argo (DONE) * Update review workflow (mediated deposits) to handle versioning (CURRENTLY TESTING) * Add contact us page (DONE) We need to write tickets for this to continue (using round-tripping tool): * Continued progress towards mapping to/from fedora to support versioning # Stretch goals * Add type-ahead entry for FAST keyword (OCLC subject terms)

    Due by November 30, 2020
  • # Goals * Accession an object with files and see it in Argo as expected (note: object may still need additional metadata mappings, but files are present) * Map keywords into descriptiveMetadata MODS * Determine and map additional missing metadata fields into MODs * Improve 'manage release' widget in work deposit form in line with mock-up (e.g., world visibility, labels, embargo setting) * Add sub-types options when creating a new item (sub-types depend on primary item type chosen - see design doc) * Make selected sub-type editable on item form (also as shown in design doc) * Ongoing cocina mapping work * Ability to work with draft items (e.g. save draft without validation) * Render the work show page as it appears in the mock-up (instead of the placeholder page that currently shows the data fields) # Stretch goals * Mediated deposit * Add type-ahead entry for FAST keyword (OCLC subject terms)

    Due by November 13, 2020
  • # Goals * App can accession a metadata-only deposit (and we can see it in Argo as expected) * Application repo has expected characteristics (CI, honeybadger, etc.; see Bootstrap epic) * Ensure all three deployment environments are ready for the application (depends on Ops cycles) * Add authorization based on LDAP workgroups * Add user generated keywords to work deposit form and see them in Argo in descriptiveMetadata (mapped to MODS) * Manage depositors in collections (add/remove) * Improve file upload widget in work deposit form in line with mock-up (e.g., description fields, ability to hide files) # Stretch Goals * Application has a feature flag (in config) that controls whether objects may be accessioned/updated/managed (to prevent changes in production before the P.O. is ready) * Application deployed to all three environments for testing (with feature flag for deposit/update turned off in production in shared_configs)

    Due by October 30, 2020
  • Focuses for sprint #4 Prescat - continue in-progress tickets - prioritize coding tickets over remediation tickets - possible prescat OS upgrades (working out process with Ops) SURI migration - preparation for SURI migration (scheduled for June 15-19) Argo - Blacklight 7 tickets - Registration scalability (if time in second week of sprint) Stretch goals - prescat remediation tickets (lower priority than coding)

    Due by June 12, 2020
  • Preservation migration - Complete first migration weekend - Done Preservation maintenance - preservationAuditWF fixes - Done Bug fixes and error reporting - Argo - verify-apo race condition - preservation-ingest-initiated not resettable in Argo - Argo web forms show current values for existing data - WAS - Fixed was-registrar#221 (resource_ids) - cdx + metadata extractor errors -- blocked by #221 - ETD - Preparation work for new step to be added in June SDR Evolution - registration uses Cocina model

    No due date
  • Google Books: - complete devops docs - IN PROGRESS -- nagios monitoring: disk on GB and SDR API -- SLA levels - Update symphony with current status on the symphony side - IN PROGRESS - Enable technicalMetadata service in production - DONE - Enable Google Books in production - DONE - Bug fixes discovered after deployment - IN PROGRESS - Make Google Books repo private - DONE SDR Evolution: - Continued expanding number of cases covered by infra-integration testing - IN PROGRESS - Continued ETD update analysis and planning - DONE - Work with Goobi to enable use of new dor-services-app endpoint for re-accessioning - DONE - Testing the migration to the new data model - IN PROGRESS -- Run all existing objects through the cocina mapper to see where the gaps are -- Set up a design meeting (Andrew + all devs, optional) to answer questions: -- How to run the migration? -- How to chunk up/sequence the data (by object/content type, by collection, by APO, by druid alpha, by registration date, by tag)? -- Noting that web archives, ETDs, GIS, and other objects are different than others -- How can we do this work without taxing current systems? -- How to find/identify problematic gaps? -- Missing source IDs for some objects -- Do we store the mapped data for further analysis? Preservation Migration: - Complete existing known object remediation - IN PROGRESS - 2 remaining - Dry-run of the first migration weekend (NOTE: deferred until April 3) - IN PROGRESS - investigate/planning for upcoming workcycle - IN PROGRESS SDR Maintenance: - high priority bug fixes - IN PROGRESS

    Due by April 10, 2020
    7/7 issues closed
  • Google Books: - create valid Google Book objects (e.g. rightsMetadata, contentMetadata, descMetadata) - testing by Andrew - export OCR content - complete devops docs - nagios monitoring: disk on GB and SDR API - SLA levels - update symphony with current status - Additional testing of techMetadata service and turn on in production - export of objects in a given app state SDR Evolution: - Expand number of cases covered by infra-integration testing - ETDs - ETD Update Analysis and planning - update persistence layer - Lyberservices - migrate a common lyberservices-scripts use case to pre-assembly - use new dor-services-app endpoint for re-accessioning - needs testing in pre-assembly - needs to be used by goobi? - test admin tags backed by Db in staging env - Deploy all the things - Write more integration tests Preservation Migration: - Complete existing known object remediation - Dry-run of the first migration weekend (NOTE: deferred until April 3) ------------------------ Stretch goals: SDR Evolution: - Investigate autogen of cocina models from OpenAPI - SURI (rails service) - Plan and prep for migrating off of old Oracle based service - Plan and prep for move to new Rails based service - Testing the migration to the new data model - Run all existing objects through the cocina mapper to see where the gaps are - Set up a design meeting (Andrew + all devs, optional) to answer questions: - How to run the migration? - How to chunk up/sequence the data (by object/content type, by collection, by APO, by druid alpha, by registration date, by tag)? - Noting that web archives, ETDs, GIS, and other objects are different than others - How can we do this work without taxing current systems? - How to find/identify problematic gaps? - Missing source IDs for some objects - Do we store the mapped data for further analysis? Preservation Migration: - investigate/planning for upcoming workcycle

    Due by March 27, 2020
    1/1 issues closed
  • Google Books: - create valid Google Book objects (e.g. rightsMetadata, contentMetadata, descMetadata) - testing by Andrew - decide what the rights and shelving attributes will be - Evaluate our copyright status computation based on further comments from Vitus - Update symphony with current status of completed books - Large batch accessioning test into stage (e.g. one day) so we can determine more confidently our actual throughput - get a priority statement from a stakeholder, translate into a query to produce barcodes, testing prioritization task to apply to database SDR Evolution: - deploy techMD service to production - use new dor-services-app endpoint for re-accessioning in pre-assembly - update cocina model to have more consistent naming structure Pres Migration: - run through the checklist for migration with someone new to fill in any gaps and prove it is complete - investigate how new objects are placed into new storage mount during migration period - continue with Moab remediation on errored out objects

    Due by March 13, 2020
    11/11 issues closed
  • ## Goals: Google Books: - create valid Google Book objects (e.g. rightsMetadata, contentMetadata, descMetadata) - testing by Andrew - decide what the rights and shelving attributes will be - Have prod server provisioned and app deployed - Update symphony with current status of completed books SDR Evolution: - decouple common-accessioning robots from DOR/Fedora 3 - complete evaluation of experiments around default rights, default descriptive metadata, and technical metadata to inform this decoupling - Use Sigfried to do file identification - Staging server for technical metadata up and running - Wire up robots to tech metadata service - make change to workflows to support this - decouple dor_indexing_app from DOR/Fedora 3 (need to determine what to index first) (STRETCH)

    Due by February 28, 2020
    39/39 issues closed