Page History

...

...

ACTION ITEMS:

TODO flesh out scenarios/examples so that we can have any requirements for order and verbosity reflected in our recommendations.

...

Agenda

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

• ACTIONS ACTION from last meeting: add type assertions to the create patch examples. DONE: https://github.com/LD4/entity_metadata_management/pull/74
• ACTION from last meeting: 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. DONE: https://gist.github.com/sfolsom/c91be2d1dd0f6984fdcd5a367d34cbae
• Inconsistency with Deprecate: related link, https://github.com/LD4/entity_metadata_management/issues/53
  • Discuss examples and as:target
    • Examples: https://gist.github.com/sfolsom/c91be2d1dd0f6984fdcd5a367d34cbae
      • TODO JSON for multiple types needs to be and array.
      • Multi typing is probably not the best way to work through the Deprecation, Merging, and Splitting. They may happen over time. Creations of objects that  are the new targets needs to happen before Splits and Merges.
        • X and Y replaced by Z (full merge), X and Y are deprecated
        • Parts X are now considered Z (partial Split)
        • Parts X are now considered Z (Partial split), and all of Y are Z (replaced), Y is deprecated
        • X is now either Y or Z (full Split), X is deprecated
        • What happens in the moment?
          • E.g. two names for the same person. You deprecate one and then point to the remaining authority
          • E.g. undifferentiated name, some of the things linked to can now be attributed to a specific other name.
          • E.g. undifferentiated name, all thinks linked to are now attributed to two or more other names.
          • E.g. undifferentiated name, status changed to because everything is attributed to 
          • E.g. shared pseudonyms TODO flesh out possible changes that occur related to shared pseudonyms.
          • E.g. two units within and organization, the two existing units are collapsed into one (the authorities remain), and a new one is used.
            • Time period for applicability can be recorded. 
    • Slack discussion: https://ld4.slack.com/archives/C013QK9Q0SX/p1674241781658209
  • (From previous 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?

...

• 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 TangKevin Ford

Nancy Falgren

Dave Eichmann

...