Describe how to handle duplicate datasets with delete-from-index

[mobb]

related to: EDIorg/ECC#10

A public search turns up duplicate datasets, which are not intended. Deprecated dataset scope.docid-A.rev is supposed to be replaced by dataset scope.docid-B.rev

the solution (to the duplicate) is technically called a"delete" although datasets are only "deleted-from-index" (they are not actually deleted, only archived).

pasta can handle revisions between the same docid, but not across docids. So if there is to be a trace from B back to A, the housekeeping task has to be handled by the site.

This process needs to get written up:
The site has two steps:

1. make the linkage between a deprecated A and replacement B.
2. request that A be deleted-from-index (I think this is a manual process for pasta devs to do)

TBD:

• where in metadata?
  • human readable?
  • machine readable?
• how is reason described?
• use cases: add examples and and list of reasons why B is likely to be deprecating A.