EasyDMP is based around a question/answer format, and each question has a type, for instance single-choice, multiple-choice, yes/no, date range, url, or typed value fetched from external API via the EEStore. A set of questions are collected into a "section", which is collected into a "template". The answers per plan are stored as JSON and is perfectly machine readable but since there is no ontology or vocabulary it is not machine actionable. In addition a free text version is generated for use as an attachment to funding applications.
It'd be handy to have types for: quota (number plus type, say), email address, cost (currency, value), keywords, language, controlled vocabulary locally stored etc., many possiblities.
This should be relatively easy for a newcomer to EasyDMP.
EasyDMP is based around a question/answer format, and each question has a type, for instance single-choice, multiple-choice, yes/no, date range, url, or typed value fetched from external API via the EEStore. A set of questions are collected into a "section", which is collected into a "template". The answers per plan are stored as JSON and is perfectly machine readable but since there is no ontology or vocabulary it is not machine actionable. In addition a free text version is generated for use as an attachment to funding applications.
It'd be handy to have types for: quota (number plus type, say), email address, cost (currency, value), keywords, language, controlled vocabulary locally stored etc., many possiblities.
This should be relatively easy for a newcomer to EasyDMP.