diff options
author | Bryan Newbold <bnewbold@robocracy.org> | 2021-11-24 15:19:26 -0800 |
---|---|---|
committer | Bryan Newbold <bnewbold@robocracy.org> | 2021-11-24 15:19:26 -0800 |
commit | a367c366852eaaeeecd4c6142ebac187df7dcf71 (patch) | |
tree | bcf5ea3582499674a3df5ff469c523581e7fb8d7 | |
parent | 9588a6a1aa01900b0dc376981635db8b609919f5 (diff) | |
download | fatcat-a367c366852eaaeeecd4c6142ebac187df7dcf71.tar.gz fatcat-a367c366852eaaeeecd4c6142ebac187df7dcf71.zip |
merger proposal typos
-rw-r--r-- | proposals/2021-11-17_entity_mergers.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/proposals/2021-11-17_entity_mergers.md b/proposals/2021-11-17_entity_mergers.md index 6c41ca58..d196d549 100644 --- a/proposals/2021-11-17_entity_mergers.md +++ b/proposals/2021-11-17_entity_mergers.md @@ -6,7 +6,7 @@ Entity Mergers One category of type of catalog metadata cleanup is merging multiple duplicate entries into a single record. The fatcat catalog allows this via during the -duplicate entities into "redirect reccords" which point at the single merged +duplicate entities into "redirect records" which point at the single merged record. This proposal briefly describes the process for doing bulk merges. @@ -78,7 +78,7 @@ be merged (redirected) to the primary release's work entity. "Grouping" releases is the same as merging their works. In this situation, the number of distinct release entities stays the same, but the duplicates are updated to be under the same work as the primary. This is initially implemented -by merging the work entites, and then updating *all* the releases under each +by merging the work entities, and then updating *all* the releases under each merged work towards the primary work identifier. No artifact entities need to be updated in this scenario. |