Skip to content
Snippets Groups Projects

Merge request for new application profile: Differential Dynamic Microscopy (DDM)

Merge request created by Dominik Braunmiller, dominik.braunmiller@rwth-aachen.de, created at 03.07.2024 16:53:47

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 Nicole Parks

Merge request reports

Loading
Loading

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 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 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 Is there an English and German version of the title and description? (English is OK, but bi-lingual is preferred.) as completed

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

  • added Waiting label

  • Nicole Parks added 1 commit

    added 1 commit

    Compare with previous version

  • Nicole Parks added 1 commit

    added 1 commit

    • 1aca5946 - fixed names; chnaged url to a property

    Compare with previous version

  • removed Waiting label

  • Nicole Parks marked the checklist item 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) as completed

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

  • Nicole Parks 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 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

  • Nicole Parks added 1 commit

    added 1 commit

    • ae44c735 - changed file location and base URL

    Compare with previous version

  • Nicole Parks marked the checklist item If applicable, contact submitter via service desk ticket (check box here and add "waiting" label to request). as completed

    marked the checklist item If applicable, contact submitter via service desk ticket (check box here and add "waiting" label to request). as completed

  • Nicole Parks 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 Does sh:targetClass URL match the base URL? (Applies in most but not all cases.) as completed

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

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

  • Nicole Parks 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 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

  • I made some minor changes, fixed the faulty IRI, subbed in some new property IRIs where I could find fitting ones, since I used classes instead of properties in the original profile that this is based on.

    We could add field descriptions, but I didn't add them to the original profile, either. Plus, they could be added at a later point in time, since they're non-destructive.

    I'm going to go ahead and merge.

    @dominik.braunmiller the profile should be available tomorrow.

  • Nicole Parks approved this merge request

    approved this merge request

  • merged

  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
  • Loading
Please register or sign in to reply
Loading