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

• Dave - order? https://github.com/LD4/entity_metadata_management/issues/34
  • Dave will work from the merged pull request.
    
    • From Slack, "I reviewed that right at the beginning of the year with the intent of discussing it on the (then) next call, but we never got to that item in the agenda since… I think the phrasing is fine as it stands, but the question is whether we discuss processing logic in the last section of the doc. (That was going to be the discussion point.)"
    • 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?
• Continue to discuss examples (updated)
  • Examples: https://gist.github.com/sfolsom/c91be2d1dd0f6984fdcd5a367d34cbae
    • TODO JSON for multiple types needs to be and array.
    • From previous meeting: 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. 

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

Nancy Falgren

Dave Eichmann

...