...
1.) Make sure the dataset is not already in QA
Go to the Authorities tab on http://elr37-dev.library.cornell.edu/ (a temporary site until http://lookup.ld4l.org/ is live) to see if the dataset of interest is already available in QA. Please, also consult the summary page (NEED LINK to page E. Lynette Rayle is creating) of datasets being supported by the LD4P2 through QA vs. those being Please consult the LD4P2 QA Authority Support Plan to confirm the dataset isn't already being supported through QA, or not currently being considered for QA because the dataset is already supported by type ahead searching already available in the BIBFRAME editor.
...
N.B. You will be asked for this information when making a formal request as a GitHub issue, see Step 5 below.
3.) Decide how contextual information should be
...
used
As you might know by now, 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 dataset's RDF. RDF descriptions of entities in the dataset.
a.) Using this spreadsheet, add a tab for the new dataset. For each new tab, please use the following column headers and value guidelines (See the existing LCGT tab in the spreadsheet as an example).
N.B. You will be asked to confirm this has been done when making a formal request as a GitHub issue, see Step 5 below.
...
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 being able the ability to declare for a particular text string searched using QA that , 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.
For example, when searching 'Casebooks' against LCGFT, http://id.loc.gov/authorities/genreForms/gf2011026115 should be in the top 10 result.
N.B. You will be asked to confirm this has been done when making a formal request as a GitHub issue, see Step 5 below.
(The Definition of YAML Keys defines how the key terms are to be used. (link coming soon.)
a.) Using the YAML key definitions above, create a YAML file for your dataset using a text editor. Save the file with the file extension .yml. and upload to https://github.com/LD4P/qa_server/tree/master/lib/generators/qa_server/templates/config/authorities/linked_data/scenarios.
b.) Alternatively, from the same page https://github.com/LD4P/qa_server/tree/master/lib/generators/qa_server/templates/config/authorities/linked_data/scenarios, create the YAML file using the GitHub "Create new" file feature.
5.) Create an issue to formally
...
request the new dataset (this will allow the request to be prioritized and tracked)
a.) From https://github.com/LD4P/qa_server/issues/new/choose, create an issue by clicking on "Get started" for the Request a New Dataset for QA. You will be asked to provide/confirm the following:
...