You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Design considerations expressed in yaml for better reading
global means stored centrally in the application for now in json local means stored in the project itself
Global storage of metadata schemas so that users can select standards from the stored list
Local storage of records related to a metadata standard
Local storage of metadata standards related to the records
Set or configure default standard (datacite)
Add new records with different standards
# DATA MODELS# This is the data structure of metadata records# When the user selects a schema, the schema will be stored centrally(globally in hardocs) # and locally in the project# A hardocs project can have a reference to different metadata schemas$schemas: # Collection of schemas stored globally
- schema1:
- schema2:
...schema:
# id: name: # For now this is going to be provided by the userurl: # provider by the userversion: # provided by the userdoi: # ??? # provided manually$path: # Automatically generated$fileName: # Generated automaticallyrecord:
$schema: # Generated automatically$path: # Generated automatically$fileName: # Will be generated automaticallydoc:
# id$title:
$fileName:
$path:
# STATE MANAGEMENT store:
docs:
doc1:
type: recordschema:
# id: name: # For now this is going to be provided by the userurl: # provider by the userversion: # provided by the userdoi: # ??? # provided manuallydoc2:
type: docdoc:
# id$title:
$fileName:
$path:
doc3:
type: record...doc4:
type: doc...doc5:
type: doc...# PHYSICAL STORAGE OF THE PROJECThardocs-fs-structure:
.hardocs: # Stores configuration of the project and structuredocs: # Stores unstructured documents html now later, also markdown, or wikis, etc, etc....
- html: # Here we store things in html
- markdown: # Here we store things in markdownrecords: # metadata records
- dublinCore:
- schema1:
# Ignore subschemas for now.....
- sub-schema1:
- sub-schema2:
- record1:
- record2:
- dataCite:
- schema1:
- schema2:
- record1:
- record2:
The text was updated successfully, but these errors were encountered:
Design considerations expressed in yaml for better reading
global means stored centrally in the application for now in json
local means stored in the project itself
The text was updated successfully, but these errors were encountered: