Local IDs - Provide for submission to collection with existing objects?

Open
#2,736 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Domain
backend

Research direction

Start by reviewing the UCB batch c2490db5-6fa4-437c-8e0d-c13d03a835f5 and the handling of its reused local identifiers across collections. No files, tests, or entry points are named; the work is complete when submissions cannot update objects in a different collection, or clearly report the conflicting local-ID data before doing so.

Written by the indexing model from the issue text.

Description

UCB batch bid-c2490db5-6fa4-437c-8e0d-c13d03a835f5 resulted in the inclusion of previously used local identifiers, which in turn caused updates to the incorrect objects in a different collection.

David noted: perhaps we should provide a check to confirm if submissions with local ID data are updating objects in the same collection to which they're being submitted? This could potentially save recovery time if such submissions are prevented.

Dominant language
JavaScript
Stars
8
Forks
4
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from CDLUC3/mrt-doc

All issues in CDLUC3/mrt-doc

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.