Sparse file output

Open
#418 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
data

Research direction

Start by locating the XML, YAML, and JSON save and load entry points, then inspect how empty attributes such as sections and values are currently serialized. Done means sparse output omits supported empty attributes while both sparse and non-sparse files load correctly across all three formats.

Written by the indexing model from the issue text.

Description

When saving odml to files, the content might include empty attributes e.g. empty sections on sections or empty values on properties.

To reduce the file sizes it might be worth to go through the possible empty attributes and support not saving them to the xml, yaml or json files.

Loading of sparse and non-sparse files need to be supported in this case.

Dominant language
Python
Stars
25
Forks
30
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from G-Node/python-odml

All issues in G-Node/python-odml

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.