Skip to content

Instantly share code, notes, and snippets.

@sfolsom
Created March 24, 2023 20:00
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save sfolsom/07338b416ca605d92984c24c346ba5fe to your computer and use it in GitHub Desktop.
Save sfolsom/07338b416ca605d92984c24c346ba5fe to your computer and use it in GitHub Desktop.
Flat_Activities_Illustrating_Activity_Types
## General comments
## Merge activities without targets gives little additional information beyond what the deprecated activity provides.
## Understanding when/what merge/split has happened requires a link between the old heading and new heading in source data.
## MARC practice is to capture this in a semi-machine-actionable way for Names in the 667 $i of the new heading "Formally..."
## For new subjects in the 010 $z (old id) and deprecated subject 682 $i (new id).
## A variant label for the previously undifferentiated heading is added to the new authority if the undifferentiated heading is deleted (1XX and 4XXs can't match).
## In LC implementation, MADSRDF seemingly points from old headings to new headings using madsrdf:useInstead for LCSH, but not Names.
## Scenario: All of X replaced by Z (full merge/replacement), X is deprecated
## Does Merge imply two or more things becoming one, or can one thing be merged into another?
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity0.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503200Z"
},
{
"type": "Deprecate",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity1.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503200X"
},
{
"type": "Merge",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity2.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503200X"
},
## Scenario: X isn't replaced by Y, instead preferred heading for X is simply updated. In some/most cases rather than deprecating the old heading the 1XX is updated instead; this could just be a change.
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity0.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503200X"
},
{
"type": "Update",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity1.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503200X"
},
## Scenario: X and Y are replaced by Z (full merge), X and Y are deprecated.
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity0.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503204Z"
},
{
"type": "Deprecate",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity1.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503210X"
},
{
"type": "Deprecate",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity2.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503215Y"
},
{
"type": "Merge",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity3.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503210X"
},
{
"type": "Merge",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity4.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/subjects/sh8503215Y"
},
## Scenario: X is now either Y or Z (full Split), X is deprecated
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity0.json",
"published": "2120-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000X"
},
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity1.json",
"published": "2123-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000Y"
},
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity2.json",
"published": "2123-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000Z"
},
{
"type": "Split",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity4.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000X"
},
{
"type": "Deprecate",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity3.json",
"published": "2123-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000X"
},
## Scenario: Parts X are now considered Z (Partial split), and all of Y are Z (replaced), Y is deprecated
## Should split and merge activities signal complete splits/merges? Partial split/merges signaled as changes? Or Deprecation signals completeness?
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity0.json",
"published": "2120-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000X"
},
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity1.json",
"published": "2123-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000Y"
},
{
"type": "Create",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity2.json",
"published": "2123-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000Z"
},
{
"type": "Split",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity4.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000X"
},
{
"type": "Merge",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity4.json",
"published": "2022-02-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000Y"
},
{
"type": "Deprecate",
"id": "https://ld4.github.io/entity_metadata_management/examples/activity3.json",
"published": "2123-03-03T15:04:18Z",
"object": "http://id.loc.gov/authorities/names/n212303000X"
},
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment