Browse and access data
The archive browser is where users search, browse, and download data hosted on the Corpus Server.
Anyone can see what is available without registering, but whether data is accessible or not depends on what access level the depositor/researcher has requested.
Being registered will not automatically permit blanket access to data. For example data sets may be open access for anyone, or even completely off limits (metadata will still be available). In general, access restrictions and conditions is decided by each, respective depositor/researcher.
There are four access levels for archived materials:
- Open: No login or registration is required
- Available to registered users
- Access needs to be requested: you can apply for access to these materials as a registered user
- Closed: These materials are currently not accessible, mostly due to the sensitivity of the material
Archiving and managing data
Uploads and management are done via the web interface Lamus. Lamus in its current form requires Java to be installed as a web-plugin. We are actively investigating upgrade paths to move aways from this requirement, but in the meantime please contact the corpus manager for further help.
Data is by default only accessible by the user managing the uploads and/or to users who already have download access to the node/s in question. Access levels can then be set to be more open or restricted, depending on what is agreed upon.
Metadata is information describing your data (data about your data). It is what allows users to locate data and is central to the archiving principle. Information that can be included but is not limited to a general description, location where the data was collected, languages spoken, participants etc.
All metadata on the Humanities Lab Corpus Server is publicly visible by design, as opposed to the actual data files where access restrictions may apply. Each depositor will have to decide whether a piece of information should be included or not in the metadata. For example, including the real name of a participant may or may not be the cause for privacy concerns, since these will also be visible to anyone browsing archive.
While the server can provide CMDI metadata "externally" to meta-archives, IMDI is the current "internal" standard. IMDI is also what you are required that you will upload together with your data. In short, no data can be added to the archive without corresponding metadata.
The corpus manager can help with workflows and options for how to create the final metadata-files. A general tip is to create a spreadsheet describing your data. Each row could contain a description corresponding to one or multiple data files. Columns represent the kinds of information you want linked to each item, such as date (YYYY-MM-DD), languages, participants, general description, location among others.