DSA logo

 

Implementation of the Data Seal of Approval

The Data Seal of Approval board hereby confirms that the Trusted Digital repository IMS Repository complies with the guidelines version 2010 set by the Data Seal of Approval Board.
The afore-mentioned repository has therefore acquired the Data Seal of Approval of 2010 on March 12, 2013.

The Trusted Digital repository is allowed to place an image of the Data Seal of Approval logo corresponding to the guidelines version date on their website. This image must link to this file which is hosted on the Data Seal of Approval website.

Yours sincerely,

 

The Data Seal of Approval Board

Assessment Information

Guidelines Version:2010 | June 1, 2010
Guidelines Information Booklet:DSA-booklet_2010.pdf
All Guidelines Documentation:Documentation
 
Repository:IMS Repository
Seal Acquiry Date:Mar. 12, 2013
 
For the latest version of the awarded DSA
for this repository please visit our website:
http://assessment.datasealofapproval.org/seals/
 
Previously Acquired Seals:
  • Seal date:March 12, 2013
    Guidelines version:2010 | June 1, 2010
 
This repository is owned by:
  • University of Stuttgart, Institute for Natural Language Processing
    Forschungszentrum Informatik
    Pfaffenwaldring 5b
    70569 Stuttgart
    Baden-Wuerttemberg
    Germany

    T 0049 711 685 81357
    F 0049 711 685 81366
    E ims@ims.uni-stuttgart.de
    W http://www.ims.uni-stuttgart.de/

Assessment

1. The data producer deposits the research data in a data repository with sufficient information for others to assess the scientific and scholarly quality of the research data and compliance with disciplinary and ethical norms.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

Currently, the IMS repository focuses on resources provided by the Institute for Natural Language Processing in Stuttgart (IMS) and other CLARIN-D related institutions such as the local Collaborative Research Centre 732 (SFB 732) as well as institutions and/or organizations that belong to the CLARIN-D extended scientific community. Comprehensive guidelines and workflows for submission by external contributors are being compiled based on the experiences in archiving such in-house resources.

Generally, our archiving service will only be provided for resources described by a full set of CMDI (http://www.clarin.eu/cmdi) metadata which have to contain relevant information for others to assess the scientific and scholarly quality of the resource, e.g. in terms of data format, annotation guidelines, peer-reviewed publications describing or using the resource, etc. All CMDI metadata are made publicly available via our repository’s web frontend (http://clarin04.ims.uni-stuttgart.de/fedora/objects) and can be harvested via OAI-PMH (http://clarin04.ims.uni-stuttgart.de/oaiprovider/oai?verb=Identify). Within CLARIN, this information is aggregated and can be searched online via software components such as the Virtual Language Oberservatory (http://www.clarin.eu/vlo/). Furthermore, we will usually provide access to the resource data themselves for means of download or online usage via web services (either freely available, restricted to academics, or on an individual basis).

The resource description is provided by the depositor, or by the IMS in collaboration with the depositor. The depositor is required to sign a depositor agreement (submitted for review to the University of Stuttgart’s lawyers) stating that their resource meets disciplinary and ethical norms as specified in the DFG’s Rules of “Good Scientific Practice” and the University of Stuttgart’s pertinent guidelines (“Richtlinien zur Sicherung der Integrität wissenschaftlicher Praxis”, see below). Additionally, we will review samples of the data before ingest.

Links:
- Deutsche Forschungsgemeinschaft: Rules of Good Scientific Practice http://www.dfg.de/en/research_funding/legal_conditions/good_scientific_practice/index.html
- Universität Stuttgart: Richtlinien zur Sicherung der Integrität wissenschaftlicher Praxis
http://www.ias.uni-stuttgart.de/common/qmh/html/231.htm
- Report on CLARIN Model Contracts: http://weblicht.sfs.uni-tuebingen.de/Reports/D-SPIN_R7.2.pdf

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

2. The data producer provides the research data in formats recommended by the data repository.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

The IMS repository requires compliance to the CLARIN standards recommendations for the LRT domain. These recommendations go beyond mere formats and call for standards in the following areas, please note the non-exhaustive lists of examples given in parentheses: general standards (XML, XML Schema, RelaxNG, URIs, Handles as persistent identifiers, ISO 639-3 language codes, ISO 3166 country codes), protocols (OAI-PMH, WSDL, SOAP, REST), terminology / ontologies (ISOcat, EAGLES/ISLE, GOLD), metadata (Dublin Core, OLAC, TEI, CMDI), media formats (MPEG1/2/4, JPEG, MP3), general (HTML, PDF, RTF, CSV) and LRT-specific text formats (LMF, (X)CES, TEI, EAF, LAF) and, finally, text encoding (Unicode, ASCII).

We check for compliance to these recommendations when reviewing the (meta-)data submitted for archiving. Metadata have to be provided and they have to be in CMDI format (other additional formats are possible). For non-compliant formats, we will provide advice for conversion to recommended standards where applicable or deny the request.

List of recommended formats:
- CLARIN, standard recommendations. http://www.clarin.eu/recommendations

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

3. The data producer provides the research data together with the metadata requested by the data repository.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

The data producer has to deposit not only the research data, but also metadata in a format that complies to our regulations (see above). Specifically, the metadata have to be in the CMDI format (cf. 1. above) or in a format that can be automatically transformed to CMDI. For some established formats, CMDI profiles and pertinent XSLT stylesheets are already available, e.g., for the conversion from Dublin Core to CMDI. Where this is not the case, we may assist in the creation of such profiles and stylesheets. This has to be decided on a case-by-case basis.

The CLARIN initiative provides exhaustive documentation (http://www.clarin.eu/cmdi) on how to create CMDI compliant metadata profiles and instances. Additionally, a set of tools is provided that allow data producers to easily create new or adapt existing metadata to the CMDI standard.

The compliance of the submitted metadata to a specific CMDI profile (-> XML schema) is validated as part of the ingest procedure. As an additional option, metadata in other CLARIN-endorsed formats (cf. the CLARIN standards recommendation document: e.g., TEI Headers) can be provided as the content of additional datastreams of Fedora Digital Objects in the repository. A minimal set of Dublin Core metadata, needed in order to adhere to the OAI-PMH protocol for disseminating metadata, will be created automatically during ingest if necessary.

Reference documentation:
- Dublin Core: http://dublincore.org/
- CMDI: http://www.clarin.eu/cmdi
- Conversion procedure from Dublin Core to CMDI: http://www.clarin.eu/faq/technical-infrastructure/metadata#t282n3448
- CLARIN, standard recommendations. http://www.clarin.eu/recommendations

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

4. The data repository has an explicit mission in the area of digital archiving and promulgates it.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline can be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

The mission of the IMS Repository is to serve as the repository of a CLARIN centre, specifically a CLARIN centre of Type B. “Type B centres offer services that include the access to the [language] resources stored by them and tools deployed at the centre via specified and CLARIN compliant interfaces in a stable and persistent way” (http://www.clarin.eu/system/files/CE-2012-0037-centre-types-v07.pdf).

The general mission of CLARIN-D, the German national CLARIN initiative, is to provide “linguistic data, tools and services in an integrated, interoperable and scalable infrastructure for the social sciences and humanities“ (http://www.clarin-d.de/en/home-en.html).

The IMS Repository is part of the CLARIN infrastructure and as such does not carry out promotional activities on its own, but is embedded into such activities on the national and the European level.

These activities do include but are not limited to:

- Providing exhaustive information on the CLARIN mission through websites (clarin.eu, de.clarin.eu).
-Operation and maintenance of the Virtual Language Observatory (VLO) which provides means to search for data/tools to the end user (based on the metadata provided by the resource centers/repositories that are part of CLARIN).
- Presenting data, tools and services provided by CLARIN on conferences.
- Organization of and participation in dissemination conferences that aim at getting in touch with the user communities of CLARIN.
- Organization of training courses.

Relevant Information:
- http://www.clarin.eu
- http://www.clarin-d.de
- http://www.clarin.eu/files/centres-CLARIN-ShortGuide.pdf
- http://www.clarin.eu/system/files/CE-2012-0037-centre-types-v07.pdf

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

5. The data repository uses due diligence to ensure compliance with legal regulations and contracts including, when applicable, regulations governing the protection of human subjects.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

Neither the CLARIN-D resource center nor the repository run by it, are legal entities on their own. This also holds for the Institute for Natural Language Processing (“Institut für Maschinelle Sprachverarbeitung”, IMS) where they are located. All are part of the University of Stuttgart which is a legal entity - specifically, like all public German universities, "eine Körperschaft des öffentlichen Rechts", an institution governed under public law.

Depositors must sign an agreement stating that they respect IPR (Intellectual Property Rights) and privacy issues and that they own all necessary rights required to deposit the data. In particular, data must be anonymised when applicable. Users must confirm that they will use resources only in the intended way. The depositor can choose to make the data publicly available. Alternatively, he can restrict access to the academic community or individual users. Data depositors are held responsible for compliance with any national or international legal regulations.

Guidelines and model contracts are provided for both, depositors and users on basis of the Clarin Model Contracts, see the link below. We have submitted them for review to the University of Stuttgart’s lawyers.

In case a violation of conditions is observed, the original data provider is contacted. In case the violator can be identified, further access by this person/institution will be prevented if technically possible (e.g., Shibboleth).

Documentation:
- Report on CLARIN Model Contracts: http://weblicht.sfs.uni-tuebingen.de/Reports/D-SPIN_R7.2.pdf

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

6. The data repository applies documented processes and procedures for managing data storage.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline can be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

The repository is implemented as a setup of the Fedora Commons Repository Architecture. Resource representations are stored within both a database and the file system for improved disaster recovery.

The repository software runs on its own virtual server hosted at the IMS Stuttgart. The local hard disks of the host system are organized as a RAID array for improved performance and safety. Individual parts are replaced at irregular intervals, depending on the technical requirements which are internally monitored (e.g., S.M.A.R.T. data). In case of failures, the administrators of the repository are notified and will take appropriate actions.

Backups are performed automatically to dedicated servers at the RUS (University of Stuttgart’s high performance computing centre) on a daily basis via the TVS (Tivoli Storage Manager) system.

All steps necessary regarding the ingest of new resources are documented internally and available to employees of the Stuttgart CLARIN-D centre.

Documentation:
- Fedora Commons Repository Software: http://www.fedora-commons.org/
- Backup & Archiving service at RUS Stuttgart (only German information available): http://www.rus.uni-stuttgart.de/dienste/datensicherung/

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

7. The data repository has a plan for long-term preservation of its digital assets.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline can be outsourced.

Applicant Entry

Statement of Compliance:
3. In progress: We are in the implementation phase.
Evidence:

Measures are taken to enhance the chance of future interpretability of the data. The number of accepted file formats is limited, to make future conversions to other formats more feasible. As much as possible open (non-proprietary) file formats are used. For textual resources, XML formats are used whenever possible, to make future interpretation of the files possible even if the tool that was used to create them no longer exists. Text should be encoded in Unicode to ensure future interpretability.

Access to data and metadata is provided via widely used open source software stacks (MySQL, Tomcat, Fedora Repository) that are installed on virtual machines. This maximizes the probability of long term support (updates, security fixes) for the tools being used and improves the ability to run installations of these software stacks independent from the underlying hardware/operating system.

Many parts of the CLARIN infrastructure do address the migration of data from one resource center / repository to another. Since the usage of these infrastructure services (e.g. a PID system, CMDI) is obligatory, every CLARIN center is, to a certain extent, ready to move it's digital assets to another center. This is of paramount importance in case a center/repository would be unable to continue offering its services. The virtual machines could be hosted by other centres, for example.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

8. Archiving takes place according to explicit work flows across the data life cycle.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline can be outsourced.

Applicant Entry

Statement of Compliance:
3. In progress: We are in the implementation phase.
Evidence:

The IMS Repository uses Fedora Commons as an underlying repository system. Our technical workflows are currently being developed on top of the pertinent built-in batch utilities for ingest and the API-M REST interface provided by the system.

For the time being, we have only internal documentation on the ingest of a resource and its corresponding metadata.

Overall, an workflow will have to contain at least the following steps: packaging/updating of the resource, creating the metadata (where necessary), doing a quality check of the data and metadata (e.g. validation, if applicable), registering PIDs (Persistent Identifiers) according to the EPIC handle system and, accordingly, providing them in the CMDI metadata format. Access to the research data has to be determined in accordance with the license chosen by the depositor. Metadata always have be publicly available. Access to the research data can be limited to users associated with research institutions (CLARIN-AAI, DFN-AAI), for example.

The handling of requests to deposit data that does not fall within the CLARIN mission will be decided on a case by case basis. Data that supports the CLARIN mission will be prioritized.

Before starting the technical ingest procedure, a human reviewer shall probe the data submitted by external providers for basic compliance to the depositor’s description.

There is currently no formal curation policy regarding when to deprecate data formats and how to deal with such data.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

9. The data repository assumes responsibility from the data producers for access and availability of the digital objects.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

The data provider retains all intellectual property rights to their data. The depositor must grant distribution rights to the repository and choose an access model (public, academic, individuals). Access models are provided by the repository and distribution rights are specified in the distribution and license agreement. The agreements also state that the purpose of the storage of a resource in the IMS repository is to make the resource available to the scientific community as it is feasible. There is no guarantee that resources are distributed, that is, the IMS reserves the right to restrict the distribution for ethical or technical reasons. In general it is the IMS' policy to only accept resources that are available for scientific usage.

Crisis management is based on the technical solutions described in 6. above. In addition, the IMS Repository archives all metadata and data in such a way that they can be easily migrated to and mirrored at other CLARIN resource centers. All metadata and data have a persistent identifier (PID) and are stored as self contained XML files.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

10. The data repository enables the users to utilize the research data and refer to them.

Minimum Required Statement of Compliance:
2. Theoretical: We have a theoretical concept.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

Local search facilities are provided on the basis of the search interface of Fedora Commons (http://clarin-04.ims.uni-stuttgart.de/fedora/objects). In addition, the DC and CMDI metadata are provided via the OAI-PMH protocol (http://clarin04.ims.uni-stuttgart.de/oaiprovider/oai?verb=Identify). They are collected by the OAI-PMH harvester of the virtual language observatory (http://www.clarin.eu/vlo/). The search interface of the VLO provides a central starting point for searching among the aggregated resources of all CLARIN partners that offer their data in this way. The VLO also features a very useful facetted browsing functionality. For some resources “deep search” (of distributed textual content) is supported by means of the CLARIN Federated Content Search (http://www.clarin.eu/fcs) interface.

Unique persistent identifiers according to the Handle system (http://www.handle.net) are provided for the resources. This makes them citable, even if the URLs should change at some point. Where available, useful reference publications are included in the CMDI metadata.

Restricted access to resources is implemented as web-based Single-Sign-On (SSO) via Shibboleth/SAML2 (http://shibboleth.net/about/index.html) and membership in associated federations of trust.

Since usage of standardized formats is encouraged, data will be available in widely used formats.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

11. The data repository ensures the integrity of the digital objects and the metadata.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
3. In progress: We are in the implementation phase.
Evidence:

The integrity of the data is fostered immensely by using checksums (MD5) in Fedora. There is also a version control mechanism in the Fedora Commons backend. CMDI metadata are represented as a data stream within Fedora Digital Objects, and as such they can be version-controlled like all other object data.

It should be noted that we decided to do strict versioning of data, at least at the PID level, only for research data and not for metadata. That is, changes to metadata will generally not result in a new PID being registered. In contrast, changes to research data will always result in a new data stream or digital object and, accordingly, a newly registered and associated persistent identifier. However, we can still make use of the built-in Fedora-internal versioning mechanism in order to keep track of changes to the CMDI metadata files. As such, changes are transparent and old versions still accessible to the user.

Part of the archiving workflow consists in an integrity check of the data and the metadata by the archive manager. This is brought about both manually and automatically. The metadata is parsed for syntactic correctness and manually evaluated for completeness and soundness. The object data is tested for syntactic correctness if possible.

Furthermore, we are planning to make use of Nagios (http://www.nagios.org/) plugins for CLARIN-D-wide monitoring of web services in the future.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

12. The data repository ensures the authenticity of the digital objects and the metadata.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

The repository in principle makes the originally deposited objects available in an unmodified way (if the objects were in one of the accepted file types and encodings). In the case of changes in the resource data, a new data stream or digital object with a new persistent identifier will be created. When new versions are stored in the repository, previous versions are maintained by a version control system built into the repository back end. In the case that changes have to be made to the data, e.g., because a file format becomes obsolete and superseded, the original data would also be kept. For updates of the metadata only, however, we do not create a new digital object with a new persistent identifier.

Generally, the repository only accepts works from the original data producers, who are acknowledged as such by means of the element in the CMDI metadata. The data producers should also contribute the exact date and time when the resource was prepared, submitted as part of the CMDI metadata.

Currently there is no explicit check of the identity of depositors since especially in the first phase of CLARIN only data that are provided by well-known partners will be added to the repository. Once this changes, an explicit procedure for the check of depositor identities and “ownership” of the ingested data needs to be specified.
For the time being, we will often know the depositors personally from the scientific community and will be in contact with them during the ingest process. Nevertheless, no external resource will be ingested without the depositors having signed a depositor’s agreement.

A limited number of authorized and trained data managers at our repository ensure the safety of both data and repository. Access to the administration facilities of the repository is restricted to these persons only.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

13. The technical infrastructure explicitly supports the tasks and functions described in internationally accepted archival standards like OAIS.

Minimum Required Statement of Compliance:
3. In progress: We are in the implementation phase.
This guideline can be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

To the best of our knowledge, the repository complies with the OAIS reference model’s tasks and functions. It is powered by the Fedora Commons Repository software, which is compliant with the Reference Model for an Open Archival Information System (OAIS) due to its ability to ingest and disseminate Submission Information Packages (SIPS) and Dissemination Information Packages (DIPS) in standard container formats.

The data consumer has direct access to the archived objects via the web, provided that access requirements have been met.

For metadata we rely on the group of emerging standards around CMDI (ISO-CD 24622-1). The repository is part of the CLARIN infrastructure and will fulfill current and future requirements decided on by the CLARIN board.

References
- Reference Model for an Open Archival Information System (OAIS), Recommended Practice, CCSDS 650.0-M-2 (Magenta Book) Issue 2, June 2012 http://public.ccsds.org/publications/archive/650x0m2.pdf
- Fedora Commons: http://fedora-commons.org/

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

14. The data consumer complies with access regulations set by the data repository.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

All CMDI metadata are provided without access restrictions according to CLARIN-D policies. However, for all deposited research data, data depositors need to specify an appropriate licence when they sign the depositor’s agreement. Some resources will have restricted access (academic, individuals vs. public) accordingly. This is supported by the repository, e.g. by Shibboleth-based means. Data users have to adhere to the licences of individual resources which they use/download via the repository. The users agree to this before access to the data is granted, cf. the End-User Agreements in the CLARIN Model Contracts. http://weblicht.sfs.uni-tuebingen.de/Reports/D-SPIN_R7.2.pdf

If the data consumer should not comply with the access regulations, the only thing that can practically be done is to deny him/her further access to the IMS repository and to make the research community aware of the misuse. Further legal measures would be reserved to the data depositors.

Access to the web-based administration interface of our Fedora Commons repository is restricted to trained employees from our group, of course.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

15. The data consumer conforms to and agrees with any codes of conduct that are generally accepted in higher education and scientific research for the exchange and proper use of knowledge and information.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

There are a number of specific codes of conduct that are applicable to parts of the repository, e.g. the DFG code of conduct. The codes of conduct are in line with generally accepted codes of conduct for research data in Germany.
Any data user is bound by the terms and conditions of use of the repository, as soon as repository services or data deposited are used. In case of misuse, the user is denied further access to the repository. Further legal measures remain reserved to the data depositors.

Data providers need to make sure that IPR and personality rights are respected in their deposited data.

Disciplinary and ethical rules:
- Deutsche Forschungsgemeinschaft: Rules of Good Scientific Practice http://www.dfg.de/en/research_funding/legal_conditions/good_scientific_practice/index.html
- Universität Stuttgart: Richtlinien zur Sicherung der Integrität wissenschaftlicher Praxis
http://www.ias.uni-stuttgart.de/common/qmh/html/231.htm

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments:

16. The data consumer respects the applicable licenses of the data repository regarding the use of the research data.

Minimum Required Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
This guideline cannot be outsourced.

Applicant Entry

Statement of Compliance:
4. Implemented: This guideline has been fully implemented for the needs of our repository.
Evidence:

Our general workflow does not allow for the integration of data into the repository without the specification of access criteria and without providing an appropriate license. If applicable, the data consumer is made aware of usage restrictions for the data s/he has gotten access to. These license conditions are available to the users of the repository, e.g. via the CMDI metadata. Generally, the usage restrictions are already described in the codes of conduct (see Section 1). For some data, explicit statements may need to be made by the data consumer about the usage of the data in terms of agreeing to a special licence agreement before s/he gets access to the data. The depositor then decides on whether access is granted or not.

In case of misuse, the only thing that can be practically done is to deny the user further access to the repository and to make the research community aware of the misuse. Further legal measures remain reserved to the data depositors.

Reviewer Entry

Accept or send back to applicant for modification:
Accept
Comments: