Thanks to visit codestin.com
Credit goes to github.com

Skip to content

WIP: UUIDs for workflows, tools, organizations, and collections #2121

@Ldcabansay

Description

@Ldcabansay

Feature Request

Desired behaviour

Currently our name fields are also the UUIDs and urls for a workflows, tools, organizations, and collections. We will need to specify and implement a defined UUID convention in order to balance between FAIR, usability, and flexibility. This relates to #1395 as aliases should link to object by UUID.

Things to consider:

  • Should UUIDs be human readable or generated (this will be relevant if we continue using UUIDs as urls)
  • Aliases should link to UUIDs
  • Should different versions of same workflow have separate UUIDs, if so how will aliases relate to different versions.

┆Issue is synchronized with this Jira Story
┆fixVersions: Open-ended research tasks
┆friendlyId: DOCK-517
┆sprint: Backlog
┆taskType: Story

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions