{"action":"opened","issue":{"url":"https://api.github.com/repos/MITLibraries/scoap3hub/issues/329","labels_url":"https://api.github.com/repos/MITLibraries/scoap3hub/issues/329/labels{/name}","comments_url":"https://api.github.com/repos/MITLibraries/scoap3hub/issues/329/comments","events_url":"https://api.github.com/repos/MITLibraries/scoap3hub/issues/329/events","html_url":"https://github.com/MITLibraries/scoap3hub/issues/329","id":101735433,"number":329,"title":"Negative Agent: detect remote duplicates","user":{"login":"JPrevost","id":1386650,"avatar_url":"https://avatars.githubusercontent.com/u/1386650?v=3","gravatar_id":"","url":"https://api.github.com/users/JPrevost","html_url":"https://github.com/JPrevost","followers_url":"https://api.github.com/users/JPrevost/followers","following_url":"https://api.github.com/users/JPrevost/following{/other_user}","gists_url":"https://api.github.com/users/JPrevost/gists{/gist_id}","starred_url":"https://api.github.com/users/JPrevost/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/JPrevost/subscriptions","organizations_url":"https://api.github.com/users/JPrevost/orgs","repos_url":"https://api.github.com/users/JPrevost/repos","events_url":"https://api.github.com/users/JPrevost/events{/privacy}","received_events_url":"https://api.github.com/users/JPrevost/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-08-18T19:51:16Z","updated_at":"2015-08-18T19:51:16Z","closed_at":null,"body":"We may want to consider an option that I think our MIT OA Collection would want.\n\nAfter creating matches, check our DSpace OA collection for a matching DOI. If it's already in our DSpace, don't deliver it... or add it to a potential duplicate queue... or something.\n\nThis could be generalized by allowing for a Channel specific DOI dedupe URL that would be checked prior to delivering.\n\nIf the Plan is to hold, maybe still hold it with a visible flag of potential duplicate.\n\nFor the volume in SCOAP3 this is not needed, but as we start discussing scaling up it would be great to not worry about what has been delivered via other mechanisms and just harvest everything in the upstream repo and passthrough anything our downstream repo doesn't have that matches... essentially allowing for backfills of articles we may have missed years ago."}}