Issue Details (XML | Word | Printable)

Key: GALAXY-378
Type: Improvement Improvement
Status: Open Open
Priority: Critical Critical
Assignee: Unassigned
Reporter: Todd Wells
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Galaxy

Allow custom metadata per-artifact

Created: 26/Sep/08 06:35 PM   Updated: 01/Dec/08 08:53 AM
Component/s: Core
Affects Version/s: 1.5-RC
Fix Version/s: 1.x Backlog

Time Tracking:
Not Specified

Labels:
User impact: Medium


 Description  « Hide
In 1.0, it appeared I could define arbitrary metadata properties per-artifact (unless I misunderstood the prior functionality). Now it seems metadata "properties" can only be defined globally by an administrator.

 All   Comments   Work Log   Change History   Transitions   FishEye      Sort Order: Ascending order - Click to sort in descending order
Dan Diephouse added a comment - 31/Oct/08 01:56 PM
Yes, this is correct. In 1.0 adding a metadata property at the per artifact level was just a shortcut for adding a global property and then assigning it a value. I think we wanted to be more careful about what type of metadata people could add.

You actually still add metadata at the per-artifact level over the API, but you won't be able to assign it a description or give it a specific type. We should maybe allow this without defining a property in the UI as well.