-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Solr: modification of fields related to access rights #462
Comments
Hi @e-maud , thanks for the detailed description of the changes. My answers:
What was the reason for changing |
Hi @theorm,
|
I think it is. We just need to make sure the app doesn't break when one of these fields is missing - basically we will be treating both of them as optional. At least to start with. |
New information regarding access rights and copyrights
...are coming in the main SOLR document index (solr2), and would need to be reflected in the middle layer.
As defined in the access-right schema, information should be displayed at newspaper and content item levels, and be shipped to both the WebApp and the API / Python Library.
Content item level (SOLR)
This is where modifications happen in solr main index, with modifications and additions of new fields.
Since field values are always the same, some short surrogates are being used. The mapping between the full values and their surrogates is currently in enums.py in the solr repo, but will move to impresso-essentials.
Information on the data domain
access_right_s
becomesdata_domain_s
.Information on copyright
copyright_detail_i'
Information on permitted use, per action:
perm_use_explore_plain
,perm_use_get_tr_plain
andperm_use_get_img_plain
.Bitmaps
Already implemented and discussed.
Questions
copyright_detail_i
OK or too cryptic / similar to bitmaps?Newspaper level (MySQL)
property_id = 36
as before) that includes data domain + permitted use, per period.Example in current new mysql:
These information should continue to be shown in the newspaper page as it is currently.
The text was updated successfully, but these errors were encountered: