Project records
Project Records
The Project records should describe the background reason WHY data we hold were collected - this could tell you about a particular field campaign, a funding program or a project - and may link to other related project records to show a programme-project-field-campaign type of hierarchy if relevant.
There are lots of cross over between the DMP tool and these records which may afford us some shortcuts in work here in due course!
These records may also hold links to relevant project resources that we or others supply - e.g. project spaces, GWS info etc.
| Field ( bold = mandatory field ) | Description | Checklist/*Controlled vocab explanations/ Notes | Y/N |
|---|---|---|---|
| Title | Short text title for the dataset collection. | Do you understand the title? Is the title brief and simple? Does the title contain unexplained technical terms or acronyms? Does the title describe the resource rather than the activity/project which produced it? Is the title in sentence case? Is the title in English? Does the title contain non-standard characters (e.g. © ° ± ² ³ µ)? |
|
| Abstract | Short text only entry that will be the first information that users will see about the text. | Do you understand the abstract? Is the abstract written in plain English? Does the abstract describe the resource rather than an activity/project which produced it? Do the first few sentences summarise the contents of the resource? Does the abstract also explain 'Where', 'When', 'How', 'Why' and 'Who' (if appropriate)? Does the abstract contain unexplained technical terms or acronyms? Does the abstract contain non-standard characters (e.g. © ° ± ² ³ µ)? |
|
| Image details | link to an image to be used as the logo | ||
| Publication State | There is a drop down box for the publication state of the data in the archive (and also the Observation Collection record). Options are | * Old * working - use this while preparing the record prior to dataset release * published - dataset details are available to users, but the content of the dataset and/or metadata may still be changing * Citable - this is ONLY to be used for dataset that are static and thus have a DOI assigned to them |
|
| Observation Collections | A filter and select option to choose which Observation Collections hold the resulting data produced by this project. If the desired Observation Collection doesn't exist then use the + button to start creating a new one (which is immediately added to the selection too) | ||
| Keywords | A list of comma separated keywords | ||
| Project Status | Controlled vocab to indicate the status of the project - should be revised to rule out ones that aren't relevant and to line up wit those in the DMP tool where possible. | * Completed * Historical Archive * Obsolete * Ongoing * Planned * Required * Under development |
|
| Parent Project | Select another Project record that acts as an parent to this record.. e.g. a Programme record for which this Project record is one of the child projects | ||
| Sub-projects (read only) | This shows a list of other project records treating this record as it's parent | ||
| Identifiers | Unless adding a DOI, or a new abbreviation, please leave these as given. | the moles2 url is to ensure that users who find an reference in a paper to a MOLES2 record using the URLs given then can confirm to themselves that they are on the equivalent MOLES3 page. | |
| Parties | A list of people/organisations (called collectively a "party") involved with the data creation or curation. Select (or create) a named party from the list, select their role from the controlled vocabulary and, if more than one party carrying out that role, use the priority number to sequence them in this role. |
* CEDA Officer - internal CEDA person responsible for the record/resource in question * Metadata Owner - party maintaining this metadata record (data centre) * Point of Contact - default is the data centre, but may be used in due course for a named person from the author list too * Principle Investigator - party leading the Project * Co-Investigator - person co-leading the project * Funder - the party funding the Project |
|
| Online Resources | Online link to relevant resource - e.g. documentation, WPS. There are set categories that should be used. Do NOT use: DMP, Download, Apply for Access - these are handled elsewhere. |
Do resource locators include titles which are concise, accurate accounts of the resource in question? Do resource locators include descriptions which fully explain their purpose? |
|
| Reviews | For carrying out metadata content reviews - not in proper operation just yet. | For the time being please refer all new records to Anabelle or Graham for a review before they are published. This is to ensure consistent quality checks are carries out | |
| Migration Properties | All the old legacy content from the MOLES2 "Content" section is in here - split into the various div tags. | Please leave the "moles2citation" at present, but look to move other items into other parts of MOLES if possible - e.g. add items under the links section to the online resources section. Once migrated feel free to delete content |