Skip to content

LINDAT/Backport ufal: refresh the Deposit page and point to recommended formats - #1685

Merged
milanmajchrak merged 2 commits into
customer/lindatfrom
lindat/fe-ufal-deposit-page
Nov 2, 2026
Merged

milanmajchrak merged 2 commits into
customer/lindatfrom
lindat/fe-ufal-deposit-page

Conversation

@milanmajchrak

Copy link
Copy Markdown
Collaborator

References

  • Backport of ufal/dspace-angular PR 183, issue 128 (ufal commit 60b2d5d)
  • Backport of ufal/dspace-angular PR 196 (ufal commit 29dfc5b)

Description

The Deposit page (EN and CS) describes the v7 UI and has new screenshots. The Upload step and the FAQ point depositors to the recommended formats in the CLARIN Standards Information System.

Instructions for Reviewers

List of changes in this PR:

  • Two ufal commits cherry-picked with -x, no conflicts. ÚFAL stays the author.
  • deposit.html, cs/deposit.html and ten step*.png screenshots are updated.
  • faq.html, cs/faq.html and the submission.sections.upload.info key in en.json5 and cs.json5 link to the CLARIN SIS format list.
  • All files and both i18n keys are the same as on ufal clarin-v7.

How to test: open /static/deposit.html and /static/cs/deposit.html, the screenshots show the v7 UI. Start a submission: the Upload step text ends with the link to the CLARIN Standards Information System.

AI Disclosure

  • No
  • Yes

Claude Code made the cherry-picks and wrote this description. The touched files were diffed against ufal clarin-v7.

Checklist

  • My PR is created against the main branch of code (unless it is a backport or is fixing an issue specific to an older branch).
  • My PR is small in size (e.g. less than 1,000 lines of code, not including comments & specs/tests), or I have provided reasons as to why that's not possible.
  • My PR follows all coding best practices based on the Code Conventions Guide
  • My PR passes ESLint validation using npm run lint
  • My PR doesn't introduce circular dependencies (verified via npm run check-circ-deps)
  • My PR includes TypeDoc comments for all new (or modified) public methods and classes. It also includes TypeDoc for large or complex private methods.
  • My PR passes all specs/tests and includes new/updated specs or tests based on the Code Testing Guide.
  • My PR aligns with Accessibility guidelines if it makes changes to the user interface.
  • My PR uses i18n (internationalization) keys instead of hardcoded English text, to allow for translations.
  • My PR includes details on how to test it. I've provided clear instructions to reviewers on how to successfully test this fix or feature.
  • If my PR includes new libraries/dependencies (in package.json), I've made sure their licenses align with the DSpace BSD License based on the Licensing of Contributions documentation.
  • If my PR includes new features or configurations, I've provided basic technical documentation in the PR itself.
  • If my PR fixes an issue ticket, I've linked them together.

🤖 Generated with Claude Code

amadulhaxxani and others added 2 commits November 2, 2026 08:58
…183)

* docs(static): refresh deposit page for v7 UI

* docs(static): fix grammar and Czech icon label per review

* docs(static): cap deposit images to container width

(cherry picked from commit 60b2d5d)
Add a sentence to the upload step info alert (en, cs) linking the LINDAT
centre page in the CLARIN Standards Information System, restoring the
format hint the DSpace 5 upload step had. Repoint the static FAQ
(en, cs) from the generic SIS recommended-formats list to the same
centre page.

(cherry picked from commit 29dfc5b)
@milanmajchrak
milanmajchrak merged commit fe1f7c4 into customer/lindat Nov 2, 2026
5 checks passed
milanmajchrak added a commit that referenced this pull request Nov 10, 2026
…ed formats (#1685) (#1700)

* docs(static): refresh deposit page for v7 UI (ufal/dspace-angular PR 183)

* docs(static): refresh deposit page for v7 UI

* docs(static): fix grammar and Czech icon label per review

* docs(static): cap deposit images to container width

(cherry picked from commit 60b2d5d)

* Point depositors to LINDAT format recommendations in upload step and FAQ

Add a sentence to the upload step info alert (en, cs) linking the LINDAT
centre page in the CLARIN Standards Information System, restoring the
format hint the DSpace 5 upload step had. Repoint the static FAQ
(en, cs) from the generic SIS recommended-formats list to the same
centre page.

(cherry picked from commit 29dfc5b)

---------



(cherry picked from commit fe1f7c4)

Co-authored-by: milanmajchrak <90026355+milanmajchrak@users.noreply.github.com>
Co-authored-by: Amad Ul Hassan <hassan@ufal.mff.cuni.cz>
Co-authored-by: Ondrej Kosarko <kosarko@ufal.mff.cuni.cz>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants