Merge request for new application profile: FASTQ Version 2

Merge request created by Catherine Gonzalez, c.gonzalez@itc.rwth-aachen.de, created at 21.05.2024 15:15:21

Note: the Review can be carried out either by checking the index.ttl file under the 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 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 in the pipeline box at the top of the merge request–just under the the . (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.

added 1 commit

• f3f02718 - Catherine Gonzalez requests new application profile FASTQ Version 2

Compare with previous version

@Heinrichs @petar.hristov This AP works on Aims. I still don't see it in the d-sp10. So I can't test it there.

@c.gonzalez don't ask me why, but retriggering the pipeline seems to have resolved it.

@Heinrichs Thanks

This is ok to merge

@c.gonzalez merged

added 1 commit

• 5e59c7fc - Add trailing /

Compare with previous version

approved this merge request

enabled an automatic merge when the pipeline for 5e59c7fc succeeds

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

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

marked the checklist item Is there an English and German version of the title and description? (English is OK, but bi-lingual is preferred.) as completed

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 Does each field have a description? as completed

marked the checklist item If pre-defined terms are used, do they make sense? (broadly speaking, e.g., dcterms:author is not used for a field named "Device".) as completed

marked the checklist item Does sh:targetClass URL match the base URL? (Applies in most but not all cases.) as completed

marked the checklist item 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}/ as completed

marked the checklist item Deploy on DSP-10 by clicking the in the pipeline box at the top of the merge request–just under the the . (add label accordingly when done) as completed

marked the checklist item 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? as completed

marked the checklist item Once review is complete, comment and tag Petar and Benedikt to approve and merge as completed

merged

mentioned in commit 059ae319