User Guide: DeSci Nodes v1.0 [Capybara]
  • Welcome to DeSci Nodes
  • General user overview
    • Explore
    • Node
      • [New] Node Home
    • Node Workspace
      • Navigation Bar
      • Viewer
      • Node Drive Panel
      • Node Contributors Panel
      • Information Panel
    • Profile
  • Create and Publish
    • Quick Start
    • Introduction
    • Sign Up & Login
    • Create a Node
      • Create Node
      • Add Components
        • Data
        • Manuscript
        • Code & Executables
        • External Links
        • Folder
      • Add Information
        • Add License
        • Add Metadata
        • Add Contributors
        • Add Comments
        • Claim Attestations
      • Organise, Access & Present
        • Return to most recent Node
        • Component Presentation
          • Pinning components
          • Renaming components
          • Moving components
        • Add Cover Art
      • Collaborate
      • Delete Before Publication
        • Delete Unpublished Components
        • [TBD] Delete Unpublished Nodes
    • Publish
      • Update Your Node
        • Editing a published Node
        • Publish a new version of your Research Node
        • Delete Components After Publication
        • Delete Published Node - Cannot
    • Submit for Curation
    • Share
      • Cite
      • Share Link
      • Persistent Identifier (dPID)
      • Content Identifier (CID)
      • Social Media
    • Interact & Reuse
      • Browse
      • Download
      • Support
        • [TBD] Comment
        • [TBD] Attest
      • Compute
        • [TBD] Node IDE
        • [TBD] Compute to data
        • [TBD] Data to compute
      • Communities
        • [TBD] Apply for Comms Curation
        • [TBD] Apply for Comms Attestations
        • [TBD] Become a Comms Member
  • Validate and Curate
    • Community Curation
    • Community Home
    • Validate and Curate
  • Find Help
    • FAQ
      • Fundamentals
      • Using Nodes
      • Nodes and Journals
      • FAIR
      • Benefits of using Nodes
      • Your identity
      • Metrics, citations and PIDs
      • Governance
    • Community Support
    • Feedback & Contact
  • TECHNICAL BACKGROUND
    • Persistent Identifiers 101
    • FAIR Data
      • All About FAIR
        • The FAIR Principles
        • GoFAIR Criteria
        • Red and Blue Principles
        • FAIR Digital Object Framework (FDOF)
        • The FAIR Hourglass
        • The Internet of FAIR Data and Services (IFDS)
      • FAIR Compliance
        • DeSci Nodes FIP
        • Standardized Assessments
        • FAIR Metadata Publishing
    • Open State Repository
      • PID
      • Data
      • Metadata
      • Methods
    • Roadmap
Powered by GitBook
On this page
  1. Create and Publish
  2. Create a Node
  3. Add Information

Add Metadata

Metadata • FAIR • Licenses

PreviousAdd LicenseNextAdd Contributors

Last updated 1 year ago

DeSci Nodes are FAIR-enabling technology. With Nodes it is easy to meet FAIR data standards by providing the relevant metadata to your work. When it comes to FAIR, metadata (the description of your data) is just as important as the actual data (artefacts) you are publishing.

Add Metadata (optional)

To add metadata to a component, in your Node Workspace open up the Information Panel on the right by clicking the icon in the address bar. You can add descriptions and licensing, as well as keywords to your component. Adding metadata is optional and we hope to automate as much of this as possible soon.

Title:

Give your component a title.

License

Here you can enter a short, textual, description of your Node component. For example its main function or contribution to the Node in a broader sense.

Since Licensing is a topic with more extensive information, please see the separate section on it. Add License

CEDAR Link

If you used a CEDAR metadata template to provide metadata for your component, you can link it here.

Ontology URL

Ontology URL: Specify the URL pointing to the relevant ontology utilized to categorize or define the component. This URL should lead to a resource providing detailed information about the ontology, facilitating clear understanding and proper contextualization of the component's categorization and semantic associations.

Description

Provide a concise yet comprehensive overview of the component. Describe its purpose, functionality, and significance within the context of the research object. Aim for clarity and relevance, ensuring that the description accurately reflects the content and intent of the component.

Keywords

To separate keywords, hit enter.

Controlled Vocabulary

Specify the predetermined set of terms or phrases used to describe this component. Utilizing a controlled vocabulary ensures consistency and precision in metadata representation. Select terms from established vocabularies or ontologies relevant to the subject matter, enhancing searchability and interoperability across datasets. Aim to adhere to established standards and guidelines for controlled vocabulary usage to promote effective data discovery and integration.

Component Type and Subtype

Components can have four Types: Document, Data, Code, and Link. When you upload a component, DeSci Nodes automatically assigns it a type based on the file extension. You may change the Type here if there was a mistake, or provide a more granular subtype (e.g., "Preprint" for a Document component).

DeSci Nodes has been designed to ensure that your publication meets FAIR standards. You won't be able to publish if you have not provided a description and license for each of your components. Keywords are optional. However, they do help increase the discoverability of your work.

Enter keywords you think are appropriate, to help with identifying, sorting and curating your work. Some guidelines for picking keywords can be found and , for example. In short from the second link: "A good rule of thumb is to use 4-6 keywords, preferably from a standardized list or database, such as , [who have great Thesaurus and Taxonomy lists], or Scopus. Avoid using words that are too general, vague, or ambiguous, such as "study", "analysis", or "model". Also, avoid using words that are already in your title, as they are redundant and waste valuable space."

here
here
MeSH
IEEE
Page cover image