Page History

...

Define the information that we want to extract from each use case

Attendees

• Aaron Birkland
• Unknown User (acoburn)
• Stefano Cossu
• Daniel Davis
• Ruth Duerr
• rlefaive
• Elliot Metsger
• Nick Ruest
• Bethany Seeger

Agenda

1. Summary of activity

   1. New use case contributions
      1.  Amherst use cases from Unknown User (acoburn)
         1. Amherst: template rendering service, 
         2. Amherst: binary derivative generation, 
         3. Amherst: ID service, 
         4. Amherst: embargo handling, 
         5. Amherst: JSON-LD compaction service, 
         6. Amherst: async digital preservation to external storage
         7. Amherst: Render fedora metadata resources as MODS/XML
      2. Transactional use case from Justin Coyne
         1. Use case: ore:aggregation locking
      3. Refined validation use cases from Stefano Cossu
         1. Enforce validation across repository
         2. Optional validation
         3. Validation only for selected resources
   2. New discussion on:
      1. Amherst: embargo handling
      2. Use case: ore:aggregation locking

2. Next Steps

   1. Close the loop, or come full circle on the AIC Use Case: Content and Structural Validation use cases
      1. Do the new use cases adequately represent the comment thread?  Anything else to do with these particular use cases at the moment?
   2. Updating Use Cases Summary - API Extension Architecture
      1. Too early? Wrong format?
   3. Review initial list  of "what to distill from use cases".
   4. Continue review
3. Any Other Business
   
   1. Elliot away: 9/28 - 10/28

...