Closed rogercgui closed 2 years ago
I think it is not recommended' but 'mandatory' that the databases involved in opac use the same prefixes for the same fields no matter how they were named (author, responsible, creator). Searches over several databases use these prefixes, so even if the field-tags are different they are indexed with the same prefix and that is why it still can work. On Sunday, March 13, 2022, 08:18:59 PM GMT+1, Roger C Guilherme @.***> wrote:
This commit advances in the construction of a usage model for the new Opac.
Important: it is recommended that the prefixes of the databases enabled in Opac are similar, i.e. "Author, creator, responsible" have the same prefix in all databases.
Important 2: the files in the opac_conf folder must be checked in installations with Opac in production. A pipe "|" was eliminated from the files because there is no need for an empty column as the original Opac presented.
You can view, comment on, or merge this pull request online at:
https://github.com/ABCD-DEVCOM/ABCD2/pull/336
Commit Summary
File Changes
(300 files)
Patch Links:
— Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you are subscribed to this thread.Message ID: @.***>
This commit advances in the construction of a usage model for the new Opac.
- For a correct operation, the indexations in the FST files were reviewed.
Important: it is recommended that the prefixes of the databases enabled in Opac are similar, i.e. "Author, creator, responsible" have the same prefix in all databases.
- Files constituting the layout were created to observe their behaviour.
- The Loanobjects database was redefined to facilitate simulations of Reservations and Renewals of items
Important 2: the files in the opac_conf folder must be checked in installations with Opac in production. A pipe "|" was eliminated from the files because there is no need for an empty column as the original Opac presented.