Date of submission of the resource.
Recommended practice is to describe the date, date/time, or period of time as recommended for the property Date, of which this is a subproperty.
Most of a resource’s dates describe moments in its public life: when it was created, issued, last modified. dcterms:dateSubmitted records an earlier and more private event, the date the resource was handed over for consideration. The usual cases are a thesis submitted to a university department and an article submitted to a journal, but the property fits any workflow where a resource passes from its author to someone who decides what happens to it next.
A refinement of date
In DCMI Metadata Terms, the property sits under dcterms:date, which itself refines dc:date. The practical effect is that software which knows nothing about submission still understands the value as a date. The formal range is a literal, and the comment points back to the recommendations for date: ISO 8601 or a published profile such as W3CDTF.
Values therefore look like 2024-04-30, or 2024-04 when only the month is known. A full timestamp with time zone is possible in W3CDTF and occasionally useful for submission systems that log the exact moment, but most catalog records stop at the day.
Where the property earns its place
Few general collections record submission dates at all. They matter in three settings:
Theses and dissertations. Universities often need to prove that a thesis was submitted before a deadline, and submission precedes examination by months. Recording it separately from the award or publication date keeps the official record accurate.
Journal and conference publishing. Many journals print “received”, “accepted” and “published” dates on each article. Mapped to Dublin Core, those become dcterms:dateSubmitted, dcterms:dateAccepted and dcterms:issued. Research on publication delays, and plain reader curiosity about how long a paper sat in review, depend on those three being separate.
Deposits and applications. Regulatory filings, grant applications and patent documents all have a submission date that carries legal weight, sometimes more than any later date.
Outside these settings the property tends to confuse more than it helps. A photograph or a website does not get submitted in any meaningful sense, and a field labeled “date submitted” on a general cataloging form invites people to type in whatever date they happen to have at hand.
Submission, accession and ingest
Repository platforms keep their own administrative dates, and it is tempting to map them onto the nearest Dublin Core term. The resulting confusion is predictable. A depositor uploading a file to an institutional repository is, from the repository’s point of view, submitting it. From the point of view of the resource, though, that upload is an accession event, which says something about the repository’s holdings and nothing about the work’s history.
A cleaner split:
| Event | Where it belongs |
|---|---|
| Author sends the work for evaluation | dcterms:dateSubmitted |
| Evaluator accepts it | dcterms:dateAccepted |
| Work is formally released | dcterms:issued |
| Repository takes a copy into its holdings | local or preservation metadata |
The last row is the one most often misfiled. PREMIS and similar schemas have explicit event types for ingest and accession, with agents and outcomes, which a Dublin Core date cannot express.
Exporting and harvesting
Simple Dublin Core has no submitted date, so a crosswalk to the fifteen elements turns it into another dc:date. A thesis record with submission, acceptance and award dates then exposes three unlabeled years to every harvester. Many repositories handle this by exporting only the issued or award date to simple Dublin Core and keeping the full set in a qualified or local format. That keeps the identifier, creator and one date consistent across systems, and the submission date stays available where a reader can see what it means.
Example in RDF
@prefix dcterms: <http://purl.org/dc/terms/> .
<https://example.org/theses/2024-017>
dcterms:title "Sediment transport in tidal channels" ;
dcterms:creator <https://example.org/people/n-haddad> ;
dcterms:dateSubmitted "2024-04-30" ;
dcterms:dateAccepted "2024-07-12" ;
dcterms:issued "2024-09-01" .
Questions about dcterms:dateSubmitted
What is dcterms:dateSubmitted?
It is the DCMI Metadata Terms property for the date a resource was submitted, for example a thesis handed to a university department or a manuscript sent to a journal. It is a sub-property of dcterms:date and of the original dc:date.
How should the date submitted be formatted?
The same way as any Dublin Core date: ISO 8601 or a profile of it such as W3CDTF. A full date like 2024-04-30 is typical; year and month alone are acceptable when the day is not known.
Is date submitted the same as date accessioned in a repository?
No. Date submitted refers to submission of the resource, usually by its author, to whoever evaluates or publishes it. The moment a repository adds a file to its holdings is an administrative event, recorded as accession or ingest in local or preservation metadata.
Which dates usually accompany dcterms:dateSubmitted?
dcterms:dateAccepted for the acceptance decision and dcterms:issued for formal publication are the common companions. Together they let a reader or a reporting system see how long review and production took for each item.
What happens to date submitted in simple Dublin Core?
When qualified records are mapped to simple Dublin Core, dcterms:dateSubmitted becomes a plain dc:date value. The event it described is lost, so exports often drop it and keep only the publication date for clarity.