ACTION ITEMS:

• ACTION: add type assertions to the create patch examples. 
• ACTION: Steven to create flat examples now with create, update, deprecate, and split. Leaning toward MAY for merge; an example can help decide.
  • Using these examples decide whether we want to recommend (MAY) to use the AS Relationship pattern.

Agenda

Discuss Issues: https://github.com/LD4/entity_metadata_management/issues

• Inconsistency with Deprecate: related link, https://github.com/LD4/entity_metadata_management/issues/53
  • (From last meeting)Continued discussion: https://github.com/LD4/entity_metadata_management/issues/68
    • To Discuss - Steven created examples to encapsulate the latest discussions- https://github.com/LD4/entity_metadata_management/issues/68#issuecomment-1357939609
    • Ended the discussion with at least the atomic change implementation. This would require any sort of change reports (for catalogers, etc.) or automation scripts to make sense of the RDF for the object entity in the Stream. If we have nested approach, we'll need to iron out the details of different types of changes and relationship between different activities, in order to create similar reports (for catalogers, etc.) or automation scripts.
    • Simeon said: "To me, the big choice is atomic or nested. The rest is details"
      • Nesting assumes full sense of the change in one place.
      • Partial processing (in the case of atomic), the incremental updates may be process before related activities have been completed
      • Terminology: we should use Flat Activities rather than "Atomic"
    • Vitus question: does "flat" mean all activities are covered by three types: create, update, deprecate? including those that are "merge" and "split"?
      • Useful to surface splits and deprecate types in order to bring attention to these types of changes in authority maintenance. SHOULD, MAY use Update
      • ACTION: add type assertions to the create patch examples. 
      • ACTION: Steven to create flat examples now with create, update, deprecate, and split. Leaning toward MAY for merge; an example can help decide.
        • Using these examples decide whether we want to recommend (MAY) to use the AS Relationship pattern.
• Dave any update on order? https://github.com/LD4/entity_metadata_management/issues/34
  • Dave will work from the merged pull request.
    
    • What more needs to be said? What this means for rdf_patch. Clear up any potential confusion around order assuming completeness (or a lack thereof).
    • Where in the document to say it. 3.2 ?
    • (Was not discussed on 2023-01-17)
• Date properties: https://github.com/LD4/entity_metadata_management/issues/39 (Was not discussed on 2023-01-17)
  
  • When to use the following in our context:
    • endTime property definition
      • Getty usage?
      • LOC usage?
    • startTime property definition
      • Getty usage?
      • LOC usage?
    • published property definition
      • Getty usage?
      • LOC usage?
    • updated property definition
      • Getty usage?
      • LOC usage?
    • deleted property definition
      • Getty usage?
      • LOC usage?

Meeting Materials

• Recommendations: https://ld4.github.io/entity_metadata_management/api/0.1/recommendations.html
• Examples: https://ld4.github.io/entity_metadata_management/api/examples.html
• Pull requests: https://github.com/LD4/entity_metadata_management/pulls
• Issues: https://github.com/LD4/entity_metadata_management/issues
• How to contribute: https://github.com/LD4/entity_metadata_management#contributing

Notes

Attendees

Vitus Tang

Kevin Ford

Nancy Falgren

Dave Eichmann

Steven Folsom