Uploaded image for project: 'Picard'
  1. Picard
  2. PICARD-2452

Can the "Submit Cluster as Release" feature be tweaked to associate custom metadata fields with the corresponding fields in the submission form?

    • Icon: Improvement Improvement
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 2.7.0b1
    • Data Submission
    • None
    • Windows 7

      I want to add some releases to MB, but since the VGMDB scripts need to be updated again, I'm instead using Picard. I have a custom metadata field called CATALOG that I would like to associate with MB's Cat. No: field to autofill it. Can this be done currently? If not, I'd like to request the ability to adjust this submission field (maybe with scripting, or a menu option where you can just type in your own associated metadata fields to use when you submit new releases).

          [PICARD-2452] Can the "Submit Cluster as Release" feature be tweaked to associate custom metadata fields with the corresponding fields in the submission form?

          Tenome added a comment -

          Hm, I guess I should just change the name of my tag anyway and match with MB. Thanks for the help.

          Tenome added a comment - Hm, I guess I should just change the name of my tag anyway and match with MB. Thanks for the help.

          Bob Swift added a comment -

          @Tenome, as a work-around for now, you could have a tagging script copy the contents of your `CATALOG` tag into the `catalognumber` tag, which would then be included in the submission. I did find a bug that Picard will not submit the catalog number if there is no `label` tag. I'll submit a fix for that. As a work-around for now you can create a `label` tag if one doesn't exist. A tagging script such as the following should do what you want:

          $if(%CATALOG%,
          $set(catalognumber,$if2(%catalognumber%,%CATALOG%))
          $set(label,$if2(%label%,No Label Set))
          )

          Bob Swift added a comment - @Tenome, as a work-around for now, you could have a tagging script copy the contents of your `CATALOG` tag into the `catalognumber` tag, which would then be included in the submission. I did find a bug that Picard will not submit the catalog number if there is no `label` tag. I'll submit a fix for that. As a work-around for now you can create a `label` tag if one doesn't exist. A tagging script such as the following should do what you want: $if(%CATALOG%, $set(catalognumber,$if2(%catalognumber%,%CATALOG%)) $set(label,$if2(%label%,No Label Set)) )

            Unassigned Unassigned
            Tenome Tenome
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:

                Version Package