Merge request for new application profile: CAD Datei

Merge request created by Johann Lehmann, johann.lehmann@rwth-aachen.de, created at 17.11.2024 23:04:20

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.

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 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 incomplete

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

Hi @johann.lehmann, I noticed a few things regarding the profile:

1. Bauteilname metadata field doesn’t have a specified type, should it be set to string?
2. Descriptions for the metadata fields are missing. Will you add those?
3. Would you consider adding the Ersteller metadata field the http://purl.org/dc/terms/creator Term IRI (dc term Ersteller) and the Veröffentlichungslizenz the http://purl.org/dc/terms/license Term IRI (dc terms licens)?
4. The IRI term link for the Datum metadata field is not working for me. Please provide a functional link

Best,
Kseniia

added 1 commit

• 1c081ac5 - added terms IRI

Compare with previous version

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 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 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 Change any other instances of the base URL to match. 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

added Deployed to D-SP10 ✔ label

added Tested on D-SP10 ✔ label

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

approved this merge request

merged

mentioned in commit f91e4297

Dear @johann.lehmann, the metadata profile is merged and will appear on Coscine tomorrow. thank you for your contribution!