Add `UUID` field to `multiscales` - moved from PR
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 171
- Forks
- 75
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 20
Description
Follow-up issue for #115. The gist:
In order to uniquely identify the images that are being generated,
this change proposes that a UUID should be included with each multiscale.
The UUID can either be generated at creation or perhaps copied from
an existing array if all meta(data) is identical (e.g. a rechunking).
In essence, the metadata would contain this:
"multiscales": [
{,
"uuid": "urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6",
"name": "example",
"datasets": [..]
}
]
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading issue #115 and the current multiscales specification to understand the proposed metadata shape and existing conventions. Define when a UUID is generated or copied, then update the specification so the UUID requirement and its behavior are unambiguous; completion means the multiscales example and normative text agree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100