Plan proceedings DOI records and verify registration separately

1. Separate the event, proceedings and individual paper

Crossref’s proceedings markup distinguishes event information, proceedings metadata and conference-paper records. Its guide identifies the event name and proceedings title, publisher and date as required, and lists contributors, title and DOI for papers. Abstracts, references, funding and licence metadata are optional but encouraged. The exact chosen schema still needs validation before a real deposit.

For the invented Methods Exchange event, record the meeting name separately from “Proceedings of Methods Exchange, Volume 1”. Each of its two papers has its own title and contributor list. If the proceedings belong to a continuing series, investigate the series identity separately; do not invent an ISSN or treat the event acronym as one.

Reference: Crossref: conference proceedings markup guide

On small screens, scroll the table horizontally, or focus it and use the arrow keys.

2. Prepare the record from the actual publication object

Use a local worksheet with a source for each field: the final title page for the title, the agreed contributor list for names and order, the publication record for the publication date, and the actual destination for the landing-page URL. Event dates and publication dates may differ. A planned publication date should remain labelled planned until its relevant event occurs.

In the fictional worksheet, Paper A has a settled title but its contributor order remains unresolved. Paper B has settled contributors but no final landing page. Neither is ready for a real deposit. Fix the missing evidence rather than filling a required field with a plausible value. The bracketed identifiers here describe a structure; they are not identifiers assigned by a registration agency.

On small screens, scroll the table horizontally, or focus it and use the arrow keys.

3. Resolve whether an abstract and full text are the same record

Crossref’s proceedings practices advise against separate records for an abstract and its full text and ask publishers to identify the publication type. They also distinguish series, volume and paper metadata. Do not treat the word “abstract” in a conference programme as enough evidence that a second independent DOI record is needed.

Suppose Paper A first appears as an abstract and is later represented by its full text as the same proceedings work in this exercise. Keep an identity note linking those stages and plan the appropriate record update. A later, substantially distinct journal article raises a different identity and relationship question; this example does not determine its publication or duplicate-publication status.

Reference: Crossref: conference proceedings and papers

4. Separate a local check from agency processing

Before a real submission, check the selected registration method and its support for the needed record type and fields. If preparing XML, validate against the intended schema and record its version and validation output. A worksheet review is not XML validation, and even valid XML may contain a wrong title or wrong destination.

This exercise stops at the worksheet: no XML has been generated or validated. In a real workflow, preserve the exact submitted payload, responsible operator and time. If a processing result is uncertain, inspect the existing submission and record before repeating the operation. A guessed retry can obscure which payload produced the current metadata.

5. Read the processing outcome for each record

Crossref’s web-deposit instructions distinguish submission to a queue from completed processing. They tell depositors to review the subsequent log to confirm successful registration. A generated XML copy is a record of the payload, not a substitute for that processing result. The guide’s form supports proceedings, but method-specific field limits must still be checked.

For an actual batch, record success or failure per object and retain the relevant message. Do not mark a volume and both papers registered merely because one item succeeded or an email arrived. In the fictional example, there is no payload or processing log, so registration remains “not performed”. This is not a simulated agency success response.

Reference: Crossref: web deposit form and submission logs

6. Verify resolution, identity and discovery independently

After a real successful registration, check that the identifier resolves to the intended landing page and that the retrieved metadata, visible title, contributors and downloadable object agree. Record the actual check time and any mismatch. Reaching an HTTP page is insufficient if it is the wrong paper, a login screen or a generic conference homepage.

Keep publication, registration, resolution and indexing as separate status fields. A functioning DOI does not establish that a named index has accepted the work, that peer review occurred or that the findings are valid. When a URL or metadata field later changes, retain the correction history and verify the updated destination rather than assuming the original receipt covers the new state.

Questions for a practical final check

• Separate event, volume, series if applicable, and paper identities.
• Source required values from the actual publication object.
• Resolve abstract/full-text identity before assigning another record.
• Record the real schema or method checks performed.
• Read processing outcomes per record.
• Check resolution and matching metadata separately from indexing.