The information returned from the LR Search API does not contain “licence” / “useRightsUrl” data. Yet, this is fundamental information, especially now that there is the GoOpen Node (where indeed “licence” is a required field). Is there any possibility / plan to include this information?
Resources published to the GoOpen Node must have the licence
specified. These data are then replicated to the public Node01 and Node02 nodes,
where “licence” / “useRightsUrl” can be correctly retrieved (in resource_data),
for example via the “obtain” service. Yet, while these resources (metadata) are also available
via the LR Search API, the information about their licence got lost [see example below].
To get this all-important information, it is possible to replicate a query to the “obtain” service for each resource retrieved from the Search API, but this is overkill. Are there better suggestions?
Thank you,
Renato
Detailed example:
Sample resource in GoOpen:
Same resource from Node01:
Same resource from LR Search (where “licence” / “useRightsUrl” is not available):
https://search.learningregistry.net/api/search?api_key=<INSERT YOUR KEY>&facet_filters[url][]=https://www.tes.com/teaching-resource/physics-revision-game-6426683
Thank you for your answer Joe.
Your proposal is appreciated, but right at the moment I cannot afford to work on that. However I am happy to share what I can with this helpful community if it can be of interest to anybody. I am conducting some narrow-focused experiments with educators, for which I am using the LR services in some (incrementally developed) prototypes. A very early one, Educational Resources Discoverer, was already made available in the Community Projects, a more advanced one, which you may also list in the Community Projects, is available here, and I am working on a further one. If anybody is interested, please let me know.
I wonder if the usage on the search service is low because people don’t know about it? For example there was somebody last year suggesting to use OpenEd API to search for Learning Registry resources, because the Learning Registry had no fine grained search API!
Renato
Hey Pat,
Joe will likely answer more extensively, however the metadata (resource_data) posted in GoOpen are supposed to be validated against this schema: resource_lrmi_open.json. I have noticed in a few cases some minor differences though, probably for resources that were introduced before the schema.
Renato