-
Notifications
You must be signed in to change notification settings - Fork 22
LINDAT FAQ
First, copy the file into the server where the repository is hosted.
If the item is still in the submission process (in user's workspace) then locate the submission from the Control Panel, Unpublished Items and edit the item. In case the item is already published, use Edit Item page. On Edit Item page select Item Bitstreams and click Upload a new Bitstream. Fill the local server form field.
Note: You have to be an administrator to be able to do this because of security and the actual workflow. Note2: You'll have to set a license
To add files to an item you are reviewing (you've already taken the task) select the submission, on the page where you can approve/curate/reject click "Edit metadata". You are in the "submission" process now, go to upload step.
If you are an admin you can follow the same steps as above (>2GB uploads) and go to edit item page through control panel.
DiscoJuice wants to store information about your SP but because it is not in a trusted federation like eduGAIN it will fail. You can disable this in aai_config.js setting instance.responseUrl to ''.
We have almost everything inside /opt/lindat-dspace
aai -> link to aai subproject (https://redmine.ms.mff.cuni.cz/projects/lindat-aai/repository)
common-theme -> link to theme subproject (https://redmine.ms.mff.cuni.cz/projects/lindat-common/repository)
configs -> directory with local.properties (inside local git repository)
handle-server -> directory with handle server configs e.g., config.dct
installation -> directory with lindat repository installation
source -> cloned this project, local properties is a symlink to configs/local.properties
E.g., adminEmail is at https://github.com/ufal/lindat-dspace/blob/lindat/dspace-oai/src/main/java/org/dspace/xoai/services/impl/xoai/DSpaceRepositoryConfiguration.java#L60
Depositing a language resource in LINDAT/CLARIAH-CZ is a guided process. You fill in metadata, upload files, choose licensing, and submit the record for editorial review. After approval, your resource is published and receives a persistent identifier (PID/handle) so that it can be reliably cited. Authenticated users with deposit access can start this process from the repository interface.
To start a new submission, first authenticate in the repository UI.
- Click Login in the top navigation bar.
- Use your institutional account (preferred) or another supported account.
- If your institution is not available, use the clarin.eu website account.
If you have trouble signing in, contact the Help Desk and include a screenshot of the error message.

After login, use the left sidebar and click New -> Item.
This is the quickest way to begin, and the collection selector dialog opens immediately.


This is an alternative to Step 2, not an additional required step.
If you prefer this route, open the left sidebar and click Submissions to open Your submissions, then click the plus button (New submission).
This also opens the collection selector.


Choose the collection where you want to deposit your resource.
- The collection list only shows places where you have submit rights.
- If you see more than one collection, choose the one whose community and collection name match your resource type.
- If unsure, contact the Help Desk: lindat-help@ufal.mff.cuni.cz.

This is the most important part of the submission. Please provide complete and accurate metadata, because metadata quality directly affects discoverability and reuse.
- Fill all required fields in the accordion sections.
- Add contact and descriptive details carefully.
- Include funding information where relevant.


For grant-funded resources, start typing the project name or grant number and use auto-complete suggestions where available:

Upload your content files in the upload section.
- Drag-and-drop files or browse from your computer.
- Check the inline file list and confirm all expected files are present.
- You can continue without files for metadata-only records when appropriate.
- If your files are very large, see How to upload files bigger than 2GB in the LINDAT FAQ.
- Use the file edit action to add short per-file descriptions when helpful.

Licensing is required to define how your resource can be used.
- Read and accept the Distribution License Agreement.
- Choose a resource license from the available list.
- If needed, open the license selector dialog to help with license choice.
If none of the offered licenses fits your needs, contact the Help Desk before completing the submission.


Note: some collections may display an additional notice message after licensing.
Before depositing, you can add a note for editors/reviewers in the submission form.
- Use the Note field for editorial context.
- Include anything that can help review (special handling, clarifications, known constraints).

When all required parts are complete, finish the process by depositing your submission.
- Confirm the footer actions show Discard, Save, Save for later, Deposit.
- Click Deposit.
- Your item then enters editorial workflow.

After editorial approval, the item is published and assigned a PID/handle for long-term reference and citation.
Tip: if you need collaboration before deposit, click Save for later, return to Submissions, and use Share submission on the workspace item.
Getting Started
Features
- All Features — full categorised list
- CLARIN Licenses
- PIDs & Handles
- Featured Services / Refbox
- Field-Level Permissions
- File Previews
- Sharing a Submission
- Personal Access Tokens
- DOI Configuration per Community
- ROR Authority
Operations
- Kubernetes Deployment
- Samples (.env, Nginx)
- Nginx + Shibboleth
- Handle Server · Setup (v7)
- Shibboleth · DiscoJuice
- Shibboleth Accounts
- S3 Storage · CESNET S3
- Google Analytics
- Matomo
- Solr
- Logging
- Custom Namespace
- Health Report
For Users
Development
Reference
- Authorizations
- Metadata Info
- Citations (proposal)
- Repository Checklist
- Search, Browse & Filters
- Localization
- Importing Items (CLI)
- OpenAIRE
- DOI Registration
- Inclusion in OLAC
- Unit Testing
- Deploy Checks
- Troubleshooting
- Versioning Theory
- Dynamic Resource Versioning
- Metashare Import · Schema
- Web Server Overview
- LINDAT Common Theme
- Workshop 2016 Results
- WebLicht Integration
- Google Dataset Search
Archive (v5 / stale)
- Old Home (v5)
- Installation (v5)
- Prerequisites (v5)
- Connecting Tomcat with Apache
- Using Apache
- Building Shibboleth FastCGI
- Shibboleth Install (v5)
- EUDAT Replication
- Backup (v5)
- Spring Social / Google Drive (v5)
- Clarin (→ Repository Checklist)
- Control Panel (v5)
- Overlays (v5)
- Configuration (v5)
- Speeding Up Downloads
- Debugging (v5)
- Selenium (v5)
- Code Contributions (v5)
- Best Practices (v5)
- Testing Hudson
- Working on Windows
- Prerequisites Checklist (v5)
- Migration to DSpace 7.2.1
- Upgrade From Lindat
- Piwik (→ Matomo) · Piwik Cleaning