Create data schemas at the Semantic Engine using our friendly user interface which walks through all the steps here
Schemas are a way to document your data and help make it more FAIR (Findable, Accessible, Interoperable, Reusable). Creating a schema is a process of continuous improvement. You don’t need to create the most perfect and complete schema at the beginning. Instead, follow this pathway to gradual improvement where each step produces something usable for researchers.
What are some benefits:
Learn what a schema is and how it can apply to your research.
Essentially, a schema describes the structure of your data and can contain helpful information such as what kind of data is in each column, what units you are using, a description of each data column and more. If you want to help people understand how to use your data you could provide them with a schema.
Following these instructions you will download the schema template (an Excel file), and based on the dataset you are describing you will enter in minimal schema information in this first iteration.
This first Excel schema will meet a lot of user needs, but how can you be sure you are all using the same version? This is something that is addressed with the OCA schema standard and the use of SAID identifiers.
Using the Excel schema that you created when you wrote your first schema, you can use the OCA parser to generate the OCA Schema Bundle.
Your Excel schema is still a human readable version of the schema, but the OCA Schema Bundle is a machine actionable version of your schema and includes special SAID identifiers helpful for schema versioning and referencing.
You can verify the integrity of an OCA Bundle by using the validate function of the OCA Browser.
Also see the section “Learn about SAID identifiers” below for more information on one of the principles of verifying an OCA Bundle.
Read about Identifiers and SAID identifiers, how they relate to the OCA schema, and how they are unique digital fingerprints of your schemas.
Read our advice and instructions on multiple ways to save, deposit, and/or publish your schema for archiving and/or public reference.
You can save your schema together with your data wherever you store your data, be it in a folder on your laptop, a shared drive, cloud storage or in a repository. Alternatively, you can put your schema separately in a repository, especially if it is suitable for others to use.
Be sure to save both the Excel Template that you created and the OCA schema bundle. The Excel Template will eventually be depreciated as we continue to build the Semantic Engine, but for now it is the best human-readable version of the schema. It can also be the starting place for adding to your schema.
After you have created a data schema, you can put it to use. Not only will it act as a reference for you and others when looking at the associated data, but you can also use it to generate a schema compliant Excel workbook for data entry.
For example, your lab may want everyone to record their -80 freezer samples using the same schema. The lab collaborates to write a schema that captures all the information they need for their samples. It includes things like a drop-down list of freezers in the lab, box labels, freezer positions, associated project names, sample collector etc. The schema is put on a common lab folder. Any new student to the lab can create a ‘data entry Excel’ from this schema which includes helpful descriptions from the schema, appropriate drop-down lists etc. All students in the lab can combine their data together to create a master sample list easily because by using the ‘data entry Excel’ they have all created schema conformant data that is easily merged.
Currently in development, when you create your OCA schema using the XLS to OCA Converter there is an checkbox option to “Generate Data Entry File”. This will create an Excel file suitable for data entry which conforms to the schema that you uploaded.
A feature that you can add to your schema template is to add the ability to only allow data entries from a select list that you define (Entry Codes).
For example, you may want to limit gender choices to a few and you don’t want some entries to say ‘M’ and other entries ‘male’ and other entries ‘masculine’ etc. This would make your analysis more difficult, especially if you are creating a data schema for use by other researchers. The solution is to create custom dropdown lists in your schema Excel template.
An example of drop-down menus in use: when you create a ‘data entry’ sheet in Excel based on your schema, your drop-down menu items will be automatically created and therefore make data entry easier and less prone to errors.
You can control the formatting of the data by modifying the format overlay.
In an Excel Template, you could choose to add format values to certain attributes. Format values restrict the formatting of the data, and any data entries that do not conform to the format will be filtered out during OCA data set validation.
Work is ongoing.