Duplicate Accession Conflict Detector
Detect exact strict accession identity conflicts across source rows without silently normalizing malformed identifiers; no conflict resolution or ownership decision.
Description
Duplicate accession identifiers create identity conflicts across records.
Duplicate accession identifiers create identity conflicts across records. Exact format validation should precede conflict detection.
Detect exact strict accession identity conflicts across source rows without silently normalizing malformed identifiers; no conflict resolution or ownership decision.
When to use Duplicate Accession Conflict Detector
Use this tool to detect exact strict accession identity conflicts across source rows without silently normalizing malformed identifiers; no conflict resolution or ownership decision.
Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
How to use Duplicate Accession Conflict Detector and understand its results
- Prepare the collection, exposure, scheduling or financial records required for this calculation. Keep row order and the declared units consistent.
- Enter recordAccessionIdentifiers using the field table and calculation rules, then run the tool.
- Read duplicateAccessionIdentifiers, conflictingRecordIndices, uniqueAccessionCount. The explanation below defines the units, signs, ordering and any flags or placeholder values.
- If the tool reports an input issue, correct the values and run it again. Apply the stated assumptions when interpreting a successfully returned result.
| Input field | Meaning | Value type; see rules below | Requirement |
|---|---|---|---|
| recordAccessionIdentifiers | Record accession identifiers | string | Required |
Enter 1–1000 nonempty trimmed newline-separated strict YYYY.lot.item identifiers. Count exact strings, return duplicate IDs in first-seen order, all conflicting zero-based row indices and distinct count.1
duplicate = exact identifier occurs more than once Units, indexing, boundary conditions and exceptional cases are defined in the calculation rules above.
| Output field | Meaning | Value type |
|---|---|---|
| duplicateAccessionIdentifiers | Duplicate accession identifiers | list of string |
| conflictingRecordIndices | Conflicting record indices | list of number |
| uniqueAccessionCount | Unique accession count | number |
{
"input": {
"recordAccessionIdentifiers": "2026.1.1\n2026.1.2\n2026.1.1"
},
"output": {
"duplicateAccessionIdentifiers": [
"2026.1.1"
],
"conflictingRecordIndices": [
0,
2
],
"uniqueAccessionCount": 2
}
}Limitations and assumptions
Malformed IDs error; no normalization, conflict resolution or ownership decision is made.
Numbers and computed results must be finite; overflow produces an error. Extremely large text inputs are rejected. Missing required fields, extra fields, wrong value types and violations of the calculation rules are input errors.
Alternative or Complementary methods
Use Accession Number Format Validator (year.lot.item): Validate exact ASCII YYYY.lot.item with year 1000–9999, positive no-leading-zero lot/item up to nine digits; reports malformed nonempty identifier as invalid without inventing corrected identity. For a complementary task, use Lot Number Next Available Finder: Find earliest unused lot in a declared accession year from actual strict item identifiers, allowing multiple items per lot; does not allocate or reserve a concurrent database identity.
References
-
Duplicate Accession Conflict Detector — tool.io
Similar or alternative tools
- Accession Number Format Validator (year.lot.item)
Validate exact ASCII YYYY.lot.item with year 1000–9999, positive no-leading-zero lot/item up to nine digits; reports malformed nonempty identifier as invalid without inventing corrected identity.
- Lot Number Next Available Finder
Find earliest unused lot in a declared accession year from actual strict item identifiers, allowing multiple items per lot; does not allocate or reserve a concurrent database identity.