To support mirroring and the upcoming time capsule, I've generated flat files for client-side filtering. Each mirror will expose a /kg/ directory from the root which will contain three files:
- digital-objects.jsonld - this is exactly the same as the old /kg/digital-objects route on HRA API.
- asctb-terms.json - An array of AS, CT, and B terms with ASCT+B type, iri, and label. This should be used for the associated filters
- kg-terms-index.json - this exposes two big properties:
term_to_purls and purl_to_terms. This will give you a lookup from digital object to terms in that DO and vice versa. This can be used for filtering based on selected terms. To save space, there is a terms and purls array which is used by the x_to_y properties as the numbers are indexes into those arrays.
The task is to replace all HRA API calls with local functions that do the same using these 3 files. For all HRA deployments and mirrors, we will use this flat file system going forward.
To support mirroring and the upcoming time capsule, I've generated flat files for client-side filtering. Each mirror will expose a /kg/ directory from the root which will contain three files:
term_to_purlsandpurl_to_terms. This will give you a lookup from digital object to terms in that DO and vice versa. This can be used for filtering based on selected terms. To save space, there is a terms and purls array which is used by the x_to_y properties as the numbers are indexes into those arrays.The task is to replace all HRA API calls with local functions that do the same using these 3 files. For all HRA deployments and mirrors, we will use this flat file system going forward.