...
Gather information about how to acquire data dumps and/or API access and the dataset's homepage URL.
N.B. You will be asked for this information when making a formal request as a GitHub issue, see Step 5 below.
...
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. Using this spreadsheet, add a tab for the new dataset. For each new tab, please use the following column headers and value guidelines (N.B. see See the existing LCGT tab 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 to declare for a particular text string searched using QA that the results should include a particular resource (identified by a URI) and what position 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.
...