|
Criterion |
Category |
Components to pay attention in evaluation |
Your evaluation: |
|
Interoperability |
Object |
· Objects and their relationships are uniquely and permanently identified· Adequate metadata for formal and content-based description· Identification of the digital objects ingests· Adequate metadata available for structural description of the digital objects acquired |
|
|
Tool |
· OAI-PMH compliant (required) |
||
|
Process |
· The assignment of metadata to the objects is guaranteed at all times· Metadata for documenting changes made on the digital objects |
||
|
Repository |
· Repository acquires adequate metadata for technical description of the digital objects· Repository acquires adequate metadata to record the corresponding usage rights and conditions· Compatibility of used metadata with other standard metadata systems |
||
|
Adaptability |
Object |
· Ease of working on code base: add/ change digital object |
|
|
Tool |
· Software and hardware tools - only common/basic software and hardware required· Possibility to add other media files (for example audio, video)· Documentation of software (M-tool, M-edit) is sufficient |
||
|
Process |
· Ability to customize look and feel - change the header, theme, footer in personalized area· Ease of publishing - inexperienced users of the repository can easily publish content· Installation, dependencies and portability |
||
|
Repository |
· Separate repository and branding for each institution |
||
|
Usability |
Object |
· Corresponds to Web Content Accessibility (W3) Guidelines (perceivable, operable, understandable, robust)· Scalable fonts and graphics |
|
|
Tool |
· Reliability of tools: maturity, fault tolerance, recoverability, availability· Cross-browser support, not dependent critically on Java Script |
||
|
Process |
· Text only navigation support· Operable to users with disabilities· Efficiency: time behavior, resource utilization· Accessibility of distributed content |
||
|
Repository |
· Transparent, accessible website· Effectively searchable repository |
||
|
Security |
Object |
· Ability to restrict access at repository item level (e.g. view metadata but not content) |
|
|
Tool |
|||
|
Process |
· The authentication used by the repository to authenticate user.· The main aspects of application security supported |
||
|
Repository |
· Backup strategies for safety of content· The infrastructure implements the security demands of the IT security system. |
||
|
Multilingual |
Object |
· Unicode text editing and storage available |
|
|
Tool |
· Ability to present multilingual object description· Description of software in several languages |
||
|
Process |
· Multilingual user interface· Multilingual search ability |
||
|
Repository |
· Localized to relevant languages |
This list is created in order to help you to express better
your opinion across the quality criteria used. But you are free to mark simply
one box in the line of scores
0
1
2
3
4
in
the interactive form of Questionnaire, provided in website, corresponding to
your informal opinion, which when formalized, means a range from “failed”
to “excellent” explained in Recommendations for Respondents.