Closed murphysj closed 8 years ago
Not sure what these requirements actually are.
think DRS. think controlled vocabulary. A real-world system needs at the very least to organize document collections by project/activity and institute. Sure for CIM.1 document we can derive a responsible party and activity from a simulation document set, but this is messy and not available for every document. pyesdoc has a simpler solution.
Hi Mark
So what is the simpler solution?
Ta, Bryan
On 20 October 2014 16:29, Mark A. Greenslade notifications@github.com wrote:
think DRS. think controlled vocabulary. A real-world system needs at the very least to organize document collections by project/activity and institute. Sure for CIM.1 document we can derive a responsible party and activity from a simulation document set, but this is messy and not available for every document. pyesdoc has a simpler solution.
— Reply to this email directly or view it on GitHub https://github.com/ES-DOC/esdoc-cim/issues/8#issuecomment-59779704.
Bryan Lawrence University of Reading: Professor of Weather and Climate Computing. National Centre for Atmospheric Science: Director of Models and Data. STFC: Director of the Centre for Environmental Data Archival. Ph: +44 118 3786507 or 1235 445012; Web:home.badc.rl.ac.uk/lawrence
These attributes are part of the DocMetaInfo class associated with each CIM vX class that is considered to be a 'document'.
WHO: Mark
These properties are currently added manually via pyesdoc but other generation methods (e.g. Questionnaire and ESMF) won't have them in there.
They are required for proper follow-on tool use.