Skip to content
Prototype metadata directory for the Research Data Alliance:
Branch: gh-pages
Clone or download
alex-ball Reconfigure MODS entry
Disciplines given in incorrect format, and in any case MODS is used
quite generally.

MARCXML and MADS are other (metadata) XML schemas, not vocabularies.

NDMSO is part of LoC, and should not be listed separately.

Contact should be name and email address, not postal address.
Latest commit 328a4a1 May 1, 2019
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
_includes
_layouts
about Add 'edit page' link to 'about' page Apr 6, 2018
css Adjust display of definition lists for clarity Oct 20, 2016
extensions Fix missing HTML tag in description Apr 6, 2017
fonts
images
js themeUpdate Jan 28, 2015
standards Reconfigure MODS entry May 8, 2019
subjects
swf Updated adding functionality Jan 26, 2014
tools
use_cases
.gitignore
Gemfile
Gemfile.lock Upgrade nokogiri dependency to avoid security issue Mar 29, 2019
LICENSE themeUpdate Jan 28, 2015
README.md
_config.yml Allow installing libraries to vendor directory Mar 29, 2019
index.md
params.json Create gh-pages branch via GitHub Jan 19, 2014

README.md

Using the Metadata Standards Directory

⚠️ Please note that the Metadata Standards Directory Working Group was succeeded by the Metadata Standards Catalog Working Group, and this Directory has been superseded by the Metadata Standards Catalog, with source code available from its development repository.

This is the source code repository for the prototype metadata directory set up by the Metadata Standards Directory Working Group of the Research Data Alliance.

Contributing to the directory

Adding a Standard

Adding a new standard is as simple as forking the repository creating a new standards file marked up with a simple YAML schema, commiting your new standard, and then submitting a pull request to the origin repository. Here is a brief set of instructions you can follow to do this:

  1. If you have not done so already, set up a GitHub account.

  2. Fork this repository using the button at the top right. It looks like this:
    Fork button

  3. In your forked copy, navigate to the 'standards' directory. To add a file, use the plus sign that appears after the path at the top of the page:
    Adding a file

  4. Give your file a sensible file name (lowercase, hyphens instead of spaces, ending in a .md extension). For the body of the file, use the template provided. Delete any bits you don't need.

    If you are unfamiliar with YAML syntax, take a look at some of the existing files or the official YAML sample file to get a feel for it.

  5. Commit the new file with a message like "Add (standard name)".

  6. Press the pull request button when it appears:
    Button to create pull request

  7. You might be asked to provide a title and description for your pull request. If so, do that and press the new "Create pull request" button.

  8. You will then see the discussion page we will use when reviewing your request. You do not have to do anything else.

If you do not have (and do not want) a GitHub account, but you have Git set up on your local machine, you can also submit a standard by cloning the repository locally, committing your changes, and performing a request-pull.

Failing that, you can tell us about standards you would like us to include by opening an issue.

Adding an Extension

By an extension, we mean a profile or other variation of a standard that enhances or extends it to provide additional functionality, or adapts it for use in a particular application or context.

The process for contributing an extension is the same as for standards. The extensions are kept in the 'extensions' directory; please use the template provided.

Adding a Tool

Tools are software tools or systems that support the use of the standard (or an extension of it) or otherwise implement it.

The process for contributing a tool is the same as for standards. The tools are kept in the 'tools' directory; please use the template provided.

Adding a Use Case

By a use case, we specifically mean a repository, data portal, organization, group, or project that uses the standard. This information is intended to give users of the directory an impression of the level of adoption, and indicate possible sources of help using the standard.

The process for contributing a use case is the same as for standards. The use cases are kept in the 'use_cases' directory; please use the template provided.

Additional help with contributing

Creating and editing files in your repository

Collaboration on GitHub

Hosting your own version

The website is generated with Jekyll. The website uses Jekyll to process HTML, YAML, and Markdown files to generate a static website.

If you choose to clone the repository running a local version of Jekyll is helpful for troubleshooting: https://help.github.com/articles/using-jekyll-with-pages

You can’t perform that action at this time.