Difference between revisions of "DPT manual Annexes"
From Archives Portal Europe Wiki
(→Annex 1: Validation errors, meaning and possible fixes) |
|||
Line 1: | Line 1: | ||
<div><br/>__TOC__<br/></div> | <div><br/>__TOC__<br/></div> | ||
== Annex 1: Validation errors, meaning and possible fixes == | == Annex 1: Validation errors, meaning and possible fixes == | ||
+ | |||
+ | {| class="wikitable collapsible sortable" | ||
+ | ! Text found in the validation tab !! Meaning !! Possible way to fix | ||
+ | |- | ||
+ | | You are using the forbidden value 'XX' in the attribute 'YY' of the element 'ZZ'. || You are using a wrong attribute value. For example, you might be using a "c" element with attribute "level" with a value "wrongValue", which is not allowed. || The value of the attribute must be correct, so try to: - Fix this in the original file if possible; - Modify the conversion stylesheet used for your purposes; - Create your own stylesheet. | ||
+ | |- | ||
+ | | The element 'XX' is missing at least one of the following sub-elements: 'YY'. || Some elements must contain mandatory elements. This message means you are not using all the mandatory elements needed. So here, element 'XX' does not contain the mandatory element 'YY'. || - Fix in original file (this element must be already missing in there); - A stylesheet does not do its job correctly and deletes elements (fix stylesheet). | ||
+ | |- | ||
+ | | The element 'XX' has been found but should not appear here, only one (or more) of the following element(s) are accepted here: 'YY'. || An element appears where it should not. For example, you can have an XML containing: [...]/scopecontent>[...]This is not allowed because should appear before . || Fix in original file so the order of the elements is correct; - A stylesheet passes elements earlier in the chain and should wait for its turn (Fix stylesheet). | ||
+ | |- | ||
+ | | The element 'XX' has been found but should not appear here, no child element is allowed here. || An element which cannot contain sub-elements does contain one. For example, element "persname" contains a sub-element "unitdate". || - Fix in original file; - Add rule in stylesheet to ignore the sub element and only copy the data of that element; - Add rule in stylesheet to copy the element or its data to another wrapper element, where it would also be fitting and allowed; | ||
+ | |- | ||
+ | | The declaration of 'XX' was not found, your file might not contain the schema declaration corresponding (xmlns). || The element 'XX' was not found at the root of the document, which means the file you are trying to validate is not using the schema. || - You can try to first convert your file, then validate it; - Your XML file does not contain the mandatory schema namespace; - You maybe try to validate an EAD file with another schema (EAG 2012 for example). | ||
+ | |- | ||
+ | | You are using the value 'XX' in an attribute that can only contain one of those values: 'YY'. || An attribute contains a wrong value. Only a value from a list can appear here and you are using a forbidden value not existing in that list. || - Fix in original file - Add rule in stylesheet to transform that special value into a not forbidden value. | ||
+ | |- | ||
+ | | Missing content for title information (unittitle): {0} || The element unittitle is empty. Note that this can be "normal", depending on your FA and the way it is structured and displayed in your system, but the result will be the display of "No title specified" in the hierarchy || - Fix in original file | ||
+ | |- | ||
+ | | Missing normalised date information (unitdate@normal): {0} || The element date is not normalised and contains only text ; the consequence is that the file is not searchable by date. Note that this can be « normal », depending on your FA and the way it is structured. || - Fix in original file - Add rules in the option “list of date conversion” | ||
+ | |- | ||
+ | | Missing information on digital object type (dao@xlink:role): {0} || The type of dao will not be analysed (thumbnail or full image) || | ||
+ | |- | ||
+ | | Wrong information on digital object link (dao@xlink:href):{0} || The link to the original document will not work because it does not begin with http://, http:// or ftp:// || - Fix in original file or - Add a rule when exporting your file to include the full url or uri | ||
+ | |- | ||
+ | | | ||
+ | |} | ||
== Annex 2: Conversion of dates - normalisation rules == | == Annex 2: Conversion of dates - normalisation rules == |
Revision as of 10:45, 3 August 2018
Contents
Annex 1: Validation errors, meaning and possible fixes
Text found in the validation tab | Meaning | Possible way to fix |
---|---|---|
You are using the forbidden value 'XX' in the attribute 'YY' of the element 'ZZ'. | You are using a wrong attribute value. For example, you might be using a "c" element with attribute "level" with a value "wrongValue", which is not allowed. | The value of the attribute must be correct, so try to: - Fix this in the original file if possible; - Modify the conversion stylesheet used for your purposes; - Create your own stylesheet. |
The element 'XX' is missing at least one of the following sub-elements: 'YY'. | Some elements must contain mandatory elements. This message means you are not using all the mandatory elements needed. So here, element 'XX' does not contain the mandatory element 'YY'. | - Fix in original file (this element must be already missing in there); - A stylesheet does not do its job correctly and deletes elements (fix stylesheet). |
The element 'XX' has been found but should not appear here, only one (or more) of the following element(s) are accepted here: 'YY'. | An element appears where it should not. For example, you can have an XML containing: [...]/scopecontent>[...]This is not allowed because should appear before . | Fix in original file so the order of the elements is correct; - A stylesheet passes elements earlier in the chain and should wait for its turn (Fix stylesheet). |
The element 'XX' has been found but should not appear here, no child element is allowed here. | An element which cannot contain sub-elements does contain one. For example, element "persname" contains a sub-element "unitdate". | - Fix in original file; - Add rule in stylesheet to ignore the sub element and only copy the data of that element; - Add rule in stylesheet to copy the element or its data to another wrapper element, where it would also be fitting and allowed; |
The declaration of 'XX' was not found, your file might not contain the schema declaration corresponding (xmlns). | The element 'XX' was not found at the root of the document, which means the file you are trying to validate is not using the schema. | - You can try to first convert your file, then validate it; - Your XML file does not contain the mandatory schema namespace; - You maybe try to validate an EAD file with another schema (EAG 2012 for example). |
You are using the value 'XX' in an attribute that can only contain one of those values: 'YY'. | An attribute contains a wrong value. Only a value from a list can appear here and you are using a forbidden value not existing in that list. | - Fix in original file - Add rule in stylesheet to transform that special value into a not forbidden value. |
Missing content for title information (unittitle): {0} | The element unittitle is empty. Note that this can be "normal", depending on your FA and the way it is structured and displayed in your system, but the result will be the display of "No title specified" in the hierarchy | - Fix in original file |
Missing normalised date information (unitdate@normal): {0} | The element date is not normalised and contains only text ; the consequence is that the file is not searchable by date. Note that this can be « normal », depending on your FA and the way it is structured. | - Fix in original file - Add rules in the option “list of date conversion” |
Missing information on digital object type (dao@xlink:role): {0} | The type of dao will not be analysed (thumbnail or full image) | |
Wrong information on digital object link (dao@xlink:href):{0} | The link to the original document will not work because it does not begin with http://, http:// or ftp:// | - Fix in original file or - Add a rule when exporting your file to include the full url or uri |