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
Downloads available from GitHub: Superraptor/GSSO > releases
Indexing information for the data source
See GSSO tab in Indexing of External Data for Look-ups
Notes
Made a very simple (label + definition) indexing request for the time being--others more familiar with the ontology may wish to add requests for indexing additional data!
Identify the data source: (Include the Data Source Name, its homepage URL, and any relevant API and/or download information to aid in caching.)
QA has the ability to provide contextual information about an entity during the look-up experience. In order to do so, decisions need to be made about how to index the RDF descriptions of entities in the dataset. Add a new tab and indexing information for the data source to the following spreadsheet: https://docs.google.com/spreadsheets/d/1rPvEoP9iYNkxJ0eWC8gXe3ci7e6mhW0da59xkGhadi0/edit?usp=sharing. (See the existing LCNAF tab in the spreadsheet as an example)
Next steps:
Once the above actions have taken place, a link to a YAML file will be shared with the requestor via a comment in the issue in order to complete Accuracy Test, https://github.com/LD4P/qa_server/wiki/Writing-Tests-for-an-Authority#accuracy-test. Edit directly the YAML file in Github, save. Create a Pull Request to be reviewed. Be sure to including a meaningful commit message (e.g. adding accuracy tests for Authority X).
Context on Accuracy Tests: In order to make sure the QA search behavior (recall and relevancy) are meeting expectations, QA uses YAML to define test parameters. These parameters include the ability to declare for a particular text string searched, the results should include a particular resource (identified by a URI) and what is the maximum position in the results the resource should be found.)
Please note, all requests for new data sources in QA will be prioritized by the LD4P2 project. Due to time restrictions there is no guarantee that all requests will be added to QA during the lifetime of the LD4P2 grant; regardless of resources it is still useful to know which datasets the community would find useful in such a lookup service.
The text was updated successfully, but these errors were encountered:
This is one of the vocabularies that the PCC Standing Committee on Standards has requested the PCC MAP working group to add to the PCC Sinopia templates, so thanks @briesenberg07 for keeping us on the loop.
Request details
Data source name
Gender, Sex, and Sexual Orientation (GSSO) Ontology
Homepage URL
https://gsso.research.cchmc.org/#!/home
Relevant API and/or download information
Downloads available from GitHub: Superraptor/GSSO > releases
Indexing information for the data source
See GSSO tab in Indexing of External Data for Look-ups
Notes
CC @AdamSchiff
INSTRUCTIONS
=============================================
Please perform each task listed below. (Email sf433 @ cornell dot edu with questions):
Next steps:
Once the above actions have taken place, a link to a YAML file will be shared with the requestor via a comment in the issue in order to complete Accuracy Test, https://github.com/LD4P/qa_server/wiki/Writing-Tests-for-an-Authority#accuracy-test. Edit directly the YAML file in Github, save. Create a Pull Request to be reviewed. Be sure to including a meaningful commit message (e.g. adding accuracy tests for Authority X).
Context on Accuracy Tests: In order to make sure the QA search behavior (recall and relevancy) are meeting expectations, QA uses YAML to define test parameters. These parameters include the ability to declare for a particular text string searched, the results should include a particular resource (identified by a URI) and what is the maximum position in the results the resource should be found.)
Please note, all requests for new data sources in QA will be prioritized by the LD4P2 project. Due to time restrictions there is no guarantee that all requests will be added to QA during the lifetime of the LD4P2 grant; regardless of resources it is still useful to know which datasets the community would find useful in such a lookup service.
The text was updated successfully, but these errors were encountered: