Skip to content
Snippets Groups Projects

Merge request for new application profile: SLE4Flame

Open Merge request for new application profile: SLE4Flame
Request/1fdbc1c9-35a7-4bbc-9987-d4d1d0dddfae into master
Open Coscine API Token requested to merge Request/1fdbc1c9-35a7-4bbc-9987-d4d1d0dddfae into master

Merge request created by Henry Axt, henry.axt@llt.rwth-aachen.de, created at 11.03.2025 12:12:01

Note: the Review can be carried out either by checking the index.ttl file under the changes tab or by copy-and-pasting the content of the file into the AIMS Frontend

  • Copy and paste code into AIMS Frontend. Check the form using under the metadata-form button. Does everything render correctly and do all the fields work?
  • Do the title and description match
  • Is there an English and German version of the title and description? (English is OK, but bi-lingual is preferred.)
  • Are various datatypes used? (If applicable, in some cases, only using string is entirely appropriate.)
  • Does each field have a description?
  • If pre-defined terms are used, do they make sense? (broadly speaking, e.g., dcterms:author is not used for a field named "Device".)
  • Does sh:targetClass URL match the base URL? (Applies in most but not all cases.)
  • If the base URL (line one in index.ttl) contains the GUID such as https://purl.org/coscine/ap/{GUID}/, modify this to contain the name of the profile and, if required, the grouping: https://purl.org/coscine/ap/{profileName}/ or https://purl.org/coscine/ap/{group}/{profileName}/
    • Change any other instances of the base URL to match.
  • Deploy on DSP-10 by clicking the arrows in the pipeline box at the top of the merge request–just under the the reactions. (add label accordingly when done)
  • Test on DSP-10 by creating a resource with the application profile and adding a file/linked data to the resource on the web interface (add label accordingly when done). Does everything render correctly and do all the fields work?
  • If applicable, contact submitter via service desk ticket (check box here and add "waiting" label to request).
  • Once review is complete, comment and tag Petar and Benedikt to approve and merge

For more details, see the documentation.

Edited by Kseniia Dukkart

Merge request reports

Pipeline #1638814 skipped

Stage: dev_deploy

Pipeline skipped for 016415ab on Request/1fdbc1c9-35a7-4bbc-9987-d4d1d0dddfae

Approval is optional
Ready to merge by members who can write to the target branch.

Merge details

  • The source branch is 2 commits behind the target branch.
  • 1 commit and 1 merge commit will be added to .
  • Source branch will not be deleted.

Activity

Filter activity
  • Approvals
  • Assignees & reviewers
  • Comments (from bots)
  • Comments (from users)
  • Commits & branches
  • Edits
  • Labels
  • Lock status
  • Mentions
  • Merge request status
  • Tracking
  • Kseniia Dukkart marked the checklist item Are various datatypes used? (If applicable, in some cases, only using string is entirely appropriate.) as completed

    marked the checklist item Are various datatypes used? (If applicable, in some cases, only using string is entirely appropriate.) as completed

  • Kseniia Dukkart marked the checklist item Copy and paste code into AIMS Frontend. Check the form using under the metadata-form button. Does everything render correctly and do all the fields work? as completed

    marked the checklist item Copy and paste code into AIMS Frontend. Check the form using under the metadata-form button. Does everything render correctly and do all the fields work? as completed

  • Kseniia Dukkart marked the checklist item Do the title and description match as completed

    marked the checklist item Do the title and description match as completed

  • Kseniia Dukkart added Waiting label

    added Waiting label

Please register or sign in to reply