Description
The structure of bibliographic metadata (neither in Aleph/Alma nor in Primo) does not comply well with adding temporary information about specific records, e.g. expected downtime or known errors. This is also the case with permanent information about e.g. options for mobile access or instructions, if you do not put it in details or similar. For the last couple of years we have utilized WordPress to enrich records in the user interface of Primo. The solution allows us to target specific records with e.g. tips for access on mobile device (e.g. using a "voucher"), broken access options, or notice about the need for registration to access certain Primo Central records from some repositories. The talk will include the following technologies: PHP, JavaScript, jQuery. However, you will not need to know these to become familiar with the solution.Presentation done at the webinar Show&Tell - an IGeLU and ELUNA Analytics, Interoperability and Linked Open Data Special Interest Working Group initiative
| Period | 17 Feb 2016 |
|---|---|
| Held at | Unknown external organisation |