extend functionality for "constructing/authoring metadata" for writing CZI
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- csharp
- Domain
- backend-api-design
Research direction
Start with the IWriter API and compare the metadata-authoring functionality available at the libCZI level and in pylibCZIrw. Review the related discussion in issue #19 before defining the scope. Done should mean that the .NET API provides documented support for constructing XML metadata when writing CZI files.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
The current API (IWriter) does not offer any help for constructing the XML-metadata.
Describe the solution you'd like
Functionality similar to what is available at libCZI-level or in pylibCZIrw.
Describe alternatives you've considered
Constructing the XML is hard, foremost because of the lack of documentation.
Additional context
#19
- Dominant language
- C#
- Stars
- 3
- Forks
- 3
- Avg merge
- 6m
- Merged PRs (30d)
- 1
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
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.
More from ZEISS/LibCZI_NET
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
ZEISS/LibCZI_NET#16 ·
All issues in ZEISS/LibCZI_NET
Similar issues
-
area/navigationview 🧭 difficulty/starter 🚀 good first issue kind/bug platform/all project/navigation-lifecycle 🧬 triage/untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
unoplatform/uno#24925 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
DamianEdwards/ghcp-spend-tray#39 ·
Maintainers usually reply within 1 day
-
copilot documentation
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 2 days
-
[Rust][Flaky Test] multiple_deadlines_fire_in_order asserts a wall-clock gap instead of firing orderOpenCI/CD ⚒️ Flaky-tests 🐦
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
valkey-io/valkey-glide#7255 ·
Maintainers usually reply within 3 days
-
bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 92/100
unoplatform/Uno.Core#99 ·