ToolJovia
Files

RIS Library Overlap Auditor

Find candidate equal-key citation records across local RIS files while preserving repeated fields, original records and file provenance.

✓ Browser-local processing
Files are read locally and are not uploaded.

Loading tool…

How to use RIS Library Overlap Auditor

Review possible overlap before combining reference exports from separate libraries. Choose bare DOI equality or an exact title/year key; the report groups matching records without deleting or merging anything. Different input files, unkeyed records and original tag evidence stay visible for a human decision.

  1. Choose one or more small RIS library exports, or load the two generated fictional examples.
  2. Choose the exact key policy and inspect candidate groups, cross-file provenance and every unkeyed reason.
  3. Download the review evidence, compare original records and make any merge decisions separately in your reference manager.

Good to know

  • Choose 1–8 well-formed UTF-8 RIS files, at most 200,000 bytes each and 400,000 bytes together. Each file has at most 4,000 lines and 300 records; all files together have at most 500 records. One initial BOM per file is recorded and removed.
  • Strict two-character uppercase/digit tags, two spaces, hyphen and an optional space/value. Every record begins with TY and ends with empty ER. Only explicitly indented, nonblank continuation lines are accepted. Unknown/repeated fields are retained; nested TY, malformed tags and unterminated records are refused.
  • DOI mode requires exactly one bare DOI-shaped DO value and folds only ASCII A–Z; it does not strip URLs or check DOI registration. Title/year mode requires exactly one TI or T1 and exactly one PY or Y1 beginning with a four-digit year. Title case, punctuation and whitespace remain exact; conflicting/repeated key fields leave a record unkeyed.
  • Equality produces candidate groups, not proof of duplicate publications. No fuzzy title matching, author reconciliation, automatic merge/removal, citation formatting or reference-manager database edit occurs. Original source and unknown field content can contain private notes or attachment paths; no attachment or URL is opened. JSON output has the shared 1,000,000-character cap.
  • Processing is local. Output is limited to 1,000,000 text characters unless a stricter file limit is stated.

Common questions

Can I automatically delete every record in a matching group except one?

No. A shared key is evidence for review, not a complete identity decision. Different versions or erroneous identifiers can share metadata. Inspect the original fields and use your reference manager’s merge workflow when appropriate.

Is this input sent to a server?

No. The application processes this input inside your browser tab and does not save it to persistent storage.

Keep going with related tools

All files →