The help page presents a set of irregular situations that could emerge during the process of validation of repositories or journals. Each item has an explanation and a justification of its need. Not all items are validated at the same time, it depends of the requested type of validation. The references to the metadata elements use the simple version of the Dublin Core scheme instead of the qualified one.

Without title

A warning message “without title” appears when a register does not present the dc.title element filled in. The recognition of the online resources is always based on a heading, it is also a mandatory item in the deposit process of repositories and journals.


Without access policy

A warning message “without access policy” appears if the register does not mention the type of access (dc.rights element). The type of access is recommended to be filled in, according to the OpenAIRE Guidelines. This information defines which type of access is associated to the item.


Without author

A warning message “without author” appears when does not exist an associated author to the register in the dc.creator element. The authorship of the work is a mandatory information in many contexts, it is used in the authorship and bibliographical references.


Without date or invalid date format

A warning message “without date or invalid date format” appears when the register does not include the dc.date element defined, or when it appears defined but not in an appropriate format. This is a mandatory field, the month and/or the day could be left in blank if were not used. The associated date to the register should be the publication date. However, there are another dates such as: the available date or the end of embargo period date, etc.


Files not accessible.

A warning message “inaccessible files” appears when it is not possible to link the file to register. This address building is associated with the permission verification functionality only available in DSpace platforms during the validation process. It can also be occurred after the files format validation through the FITS.


Without description

A warning message “without description” appears when does not exist a dc.descritpion element filled in. This field is optional but recommended to allow a better retrievability by search engines and aggregators.


Invalid access policy

In the validation report appears the error “invalid access policy” when the policy is not defined according to the openAccess terminology.


File format not recognized

A warning message “file format not recognized” appears when the register was not deposited with a proper format supported by digital preservation processes. This validation is based on validation process used by FITS tool.


Without TID

A error message “without TID” appears when an associated TID to the register in the dc.identifier.tid element in thesis/dissertations defended in or after August 7, 2013 does not exist. If only the year or month and year is specified, The TID is checked for defense dates greater than or equal to 2013 or August 2013 respectively.


Invalid type of document

A warning message “invalid type of document” appears when the register was deposited with a type of document which is not according to the DRIVER 2.0 Guidelines, essentially specific guidelines to DRIVER metadata, being a mandatory field it is asked its correction. This information appears in dc.type element and it is restricted to the types defined by DRIVER and OpenAIRE Guidelines. Can be used for other document types to different purposes than scientific production.


Invalid language

A warning message “invalid language” appears when the register contains a language format which is not included in the ISO 639-3 standard. This element corresponds to the dc.language element and should be according to the OpenAIRE Guidelines.


Embargo Incoherence

The "Embargo Incoherence" note appears when an Item has "embargoedAccess" in the dc.rights property, but has no dc.date.embargo, or it has a past date


Without language

A warning message “without language” appears when the register was deposited without a publication language. It is a mandatory field and should be filled in according to the ISO 639-3 standard using dc.language element. Please have a look at OpenAIRE Guidelines.


Invalid TID

A error message “Invalid TID” appears when there is not a valid TID associated to the register in the dc.identifier.tid element in thesis/dissertations defended in or after August 7, 2013 does not exist. If only the year or month and year is specified, The TID is checked for defense dates greater than or equal to 2013 or August 2013 respectively.


Invalid access policy

In the validation report appears the warning “invalid access policy” when the policy is not defined according to the following terminologies: openAccess, restrictedAccess, closedAccess and embargoedAccess. For further information please have a look at OpenAIRE Guidelines.


Without type of document

A warning message “without document type” appears when the item was available without type of document following the DRIVER 2.0 or OpenAIRE Guidelines, essentially the specific guidelines to DRIVER metadata. It is a mandatory field.


Item should be in Open Access

Following DRIVER, OpenAIRE or other related profiles, the item should be in Open Access, with dc-rights element filled in with the word “openAccess”.