MyDriver      

Validation > Score information
DRIVER validation score

When a repository/set is validated it receives a score, which is an indication for the DRIVER technical team and the repository manager how well the specific repository or set abides to the DRIVER guidelines.

Below you will find a short description and explanation to see how the scoring mechanism works. If you have more questions or need further explanations please contact the DRIVER helpdesk.

Score calculation

Each rule is assigned a weight. The score is estimated as the weighted average of the percentage of errors for each rule.

For example, for rules r1, r2, r3 with corresponding weights w1, w2, w3, if the percentage of errors is p1, p2, p3, then the score is calculated by the following formula:

score = (w1*p1 + w2*p2 +w3*p3) / w1+w2+w3

Although in Guidelines v2.0 some rules are optional, it is recommnended that repository managers pay attention to their implementation.
rule description weight
M
a
n
d
a
t
o
r
y
dc:identifier field exists and it is not empty 0.3
dc:title field exists and it is not empty 0.4
dc:date field exists and it is not empty 0.3
dc:type field exists and it is not empty 0.3
dc:creator field exists and it is not empty 0.3
At least one dc:type field must use one of the values defined in
http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:eu-repo
0.1
dc:type field must use one of the values defined in
http://info-uri.info/registry/OAIHandler?verb=GetRecord&metadataPrefix=reg&identifier=info:eu-repo
or in
http://www.surffoundation.nl/wiki/display/DRIVERguidelines/Version+vocabulary
Any free text is also acceptable
0.1
dc:format field must use one of the values defined in
http://www.iana.org/assignments/media-types
0.3
dc:date field appears only once, preferably containing the creation date (to reduce ambiguity) 0.2
dc:date field should use one of the formats defined in
http://www.w3.org/TR/NOTE-datetime
0.3
dc:identifier field should be used to indicate the URL of the object described in the metadata record 0.3
Author (creator) names must use a standard format 0.1
O
p
t
i
o
n
a
l
dc:language field should use one of the following ISO standards: ISO 639-1, ISO 639-2, ISO 639-3 0.3
dc:audience field should use one of the values defined in
http://www.ed.gov/admin/reference/index.jsp
0.1
We recommend that you put the Digitised resource location in the dc:identifier field. In the Source field only metadata of a formal identifier system should be placed here to describe the original resource. 0.2
Author (contributor) names must use a standard format 0.1
Implicit incorrect use in one of the dc:source or dc:identifier fields 0.1
Implicit incorrect use in one of the dc:relation or dc:identifier fields 0.1
Implicit incorrect use in one of the dc:source or dc:relation fields 0.1