Normal - Devise a strategy for existing fields. Factors to consider include:
- Currently “collection_summary” (aka “Summary” in the GUI) holds the main description of a dataset and “detailed_description” (aka “Detailed Description in the GUI) holds extra info that we thought was too much content for the main summary.
- CICADAS does not have headings for either of these things, but “Summary” is conceptually similar to “Abstract” and “Detailed Description” is conceptually relevant for holding everything else that’s in CICADAS (Introduction, Methods, Usage Notes, etc). Could these fields be renamed/repurposed? Or is that not worth the trouble compared to creating new fields?
- We could potentially leave the existing fields alone and create 2 brand new fields called “dataset_abstract” and “dataset_description” and copy the relevant info from existing fields where available for editing/polishing. This would allow a gradual preparation of content that we can switch over to once everything is ready while still leaving all the current production content in place with the existing layout/structure.
- FNL could finish its work on generating and providing any content that’s missing to ensure we have something for both fields for all datasets. Or if WP can auto-hide empty sections (I think it can?) then we could just put the existing Summary in the “dataset_description” field for legacy datasets and not display any “dataset_abstract” section on the page at all when they’re empty.
Hold meetings and develop requirements for updates to collection/analysis pages to support CICADAS template https://cancerimagingarchive.net/cicadas Devise a strategy for existing fields. Factors to consider include: See Description
-
Kirk Smith
-
- Votes:
-
0 Vote for this issue
- Watchers:
-
1 Start watching this issue
- Created:
- Updated: