Open nielsdrost opened 8 years ago
So possibly two new functions:
estep generator maximize <schema> <filename>
and
estep generator minimize <filename>
?
We have the descriptions from the schema, and YAML supports comments, so extra descriptions would be extra nice. BUT. We use objects (without comments) in the code so we have write out the YAML in another way... Also: to preserve the comments, we also have to read in the YAML in a different way.
I don't understand the difference between maximize and minimize.
I would not have a problem with creating an invalid file which the user then needs to correct.
For example:
competence: Big Data Analytic / Optimized Data Handling / Efficient Computing
discipline: Physics & Beyond / Environment & Sustainability / Life Sciences & eHealth / Humanities & Social Sciences / eScience Methodology
expertise:
- PLEASE PRUNE TO CORRECT LIST
- Text Mining
- Machine Learning
- Information Visualization
- Scientific Visualization
- Information Retrieval
- Computer Vision
- Handling Sensor Data
- Linked Data
- Information Integration
- Databases
- Data Assimilation
- Distributed Computing
- Accelerated Computing
- Low Power Computing
- Orchestrated Computing
- High Performance Computing
- Reproducible Research
Right now figuring out what I can fill in, what I need to fill in, etc is rather cumbersome.
We should perhaps add an option to the generator to "fill" a file with all possible keys from the schema. That way you at least know what you need to fill in / when you are done, etc
Perhaps even add a line with possible values / description, etc, as a comment above each key.
(edit: whoops first add content, then create ticket)