Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Table names/Protocol names unique in ARC? #66

Open
Freymaurer opened this issue Jun 21, 2023 · 2 comments
Open

Table names/Protocol names unique in ARC? #66

Freymaurer opened this issue Jun 21, 2023 · 2 comments
Assignees

Comments

@Freymaurer
Copy link
Contributor

MUST Swate table names (or protocol names in ISA-JSON) be unique in the ARC? In a study? in a assay?

@HLWeil
Copy link
Member

HLWeil commented Jan 5, 2024

For intuitiveness of usage I would argue for having the Sheet names unique in the context of a study or assay and not ARC wide.

Why not ARC-wide?

It is probably hard for users to keep track of the protocol names they used across the ARC. And these often naturally repeat (e.g. "Growth").

Why in the context of an assay/a study?

On the other hand, uniqueness in a single assay file or study file is a constraint of the file format (no duplicate sheet names in xlsx files). So users, get restrained in that regard anyways.

@HLWeil
Copy link
Member

HLWeil commented Jan 5, 2024

Of course the same "keep track" argument is also true for samples/materials. But for them, the ability to cross-reference across different assays/studies is essential, which is not the case for the protocols.

@kMutagene kMutagene added this to the ARC-specification v2.1.0 milestone Jun 12, 2024
@kMutagene kMutagene added the Status: Needs Triage This item is up for investigation. label Jun 12, 2024
@HLWeil HLWeil self-assigned this Jun 27, 2024
@HLWeil HLWeil removed the Status: Needs Triage This item is up for investigation. label Jun 27, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In discussion
Development

No branches or pull requests

3 participants