Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community_call:minutes20220503
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
community_call:minutes20220503 [2022/05/03 13:00] – [VuFind® Community Call Minutes: May 3, 2022] demiankatz | community_call:minutes20220503 [2022/05/09 16:22] (current) – [2. Authority Data Enhancements] liowalter | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== VuFind® Community Call Minutes: May 3, 2022 ====== | ====== VuFind® Community Call Minutes: May 3, 2022 ====== | ||
- | Attending: Chris Hallberg, Demian Katz, Claas Kazzer, Ere Maijala, Mario Trojan, Lionel Walter | + | Attending: Chris Hallberg, Demian Katz, Claas Kazzer, Andrii Lysohor, Ere Maijala, Mario Trojan, Lionel Walter |
===== Agenda ===== | ===== Agenda ===== | ||
Line 17: | Line 17: | ||
=== Possible Laminas Deprecations === | === Possible Laminas Deprecations === | ||
- | No news. Next step is to review progress on the pull request, when time permits. | + | No news. |
=== Citation Style Language === | === Citation Style Language === | ||
- | No news. | + | No news. Next step is to review progress on the pull request, when time permits. |
=== Blended Search === | === Blended Search === | ||
- | Blended search -- the ability to create a single result list combining records from multiple backends -- is now available in the dev-9.0 branch and will be a major new feature of VuFind 9.0. If you are interested in this capability, please test out the dev-9.0 branch and provide feedback. Thanks to Ere Maijala and the team at the National Library of Finland for contributing this major new feature. | + | Blended search -- the ability to create a single result list combining records from multiple backends -- is now available in the dev-9.0 branch and will be a major new feature of VuFind 9.0. If you are interested in this capability, please test out the dev-9.0 branch and provide feedback. [[configuration: |
==== 2. Authority Data Enhancements ==== | ==== 2. Authority Data Enhancements ==== | ||
Line 36: | Line 36: | ||
* Should we do more with the authority schema fields added by [[https:// | * Should we do more with the authority schema fields added by [[https:// | ||
* Should the authority schema be extended with any additional standard fields? | * Should the authority schema be extended with any additional standard fields? | ||
+ | * Mario has added some fields for external IDs (ORCID, VIAF, Wikidata, etc., etc.; see [[https:// | ||
+ | * Demian opened [[https:// | ||
* How should we display authority data? Do we need to integrate the RecordDataFormatter (or something like it)? Do we need some kind of plugin mechanism for dropping in related content? | * How should we display authority data? Do we need to integrate the RecordDataFormatter (or something like it)? Do we need some kind of plugin mechanism for dropping in related content? | ||
+ | * Mario has used a template-based approach for record display, with some functionality in the view helper (for generating schema.org HTML). [[https:// | ||
+ | * Ere shared [[https:// | ||
+ | * Lionel shared [[https:// | ||
+ | * Demian opened [[https:// | ||
* Can we create something like IxTheo' | * Can we create something like IxTheo' | ||
- | | + | * Mario suggested that we might want to better generalize the [[https:// |
+ | * Demian opened [[https:// | ||
+ | | ||
+ | * Mario noted that the service he built was based on an API which went offline temporarily and caused problems when a cache was cleared -- a more persistent cache might be valuable to work around this problem. | ||
* If we build a content plugin mechanism, what kinds of plugins can we build? Lists of relationships? | * If we build a content plugin mechanism, what kinds of plugins can we build? Lists of relationships? | ||
* How can we better incorporate authority data into searches? (e.g. balancing use of identifiers with textual headings) | * How can we better incorporate authority data into searches? (e.g. balancing use of identifiers with textual headings) | ||
+ | * Lionel suggested using variant names from authority records to enhance search results. | ||
+ | * Ere is working on an approach that allows authority IDs to be used in parallel with records that don't have authority IDs. This allows very specific matching without excluding less rich records. There is also a decision point where users can decide how to interact with the heading -- e.g. search as author, search as heading, find related information, | ||
* Do we need to include more standard configurations/ | * Do we need to include more standard configurations/ | ||
* Is there a better solution than indexing parallel values across multiple Solr fields for storing complex data like authors with roles/ | * Is there a better solution than indexing parallel values across multiple Solr fields for storing complex data like authors with roles/ | ||
+ | * Mario hasn't found a better solution yet; the only technical alternative is using delimited/ | ||
* Should we use more elegant URL routing for authority records (/ | * Should we use more elegant URL routing for authority records (/ | ||
+ | * Demian opened [[https:// | ||
==== 3. Other Topics? ==== | ==== 3. Other Topics? ==== | ||
Demian is hoping to work with the PMC to set a release date for 8.1 in the near future. If you have outstanding work or feature requests for inclusion in 8.1, please let someone from the PMC know as soon as possible before things get locked in place. | Demian is hoping to work with the PMC to set a release date for 8.1 in the near future. If you have outstanding work or feature requests for inclusion in 8.1, please let someone from the PMC know as soon as possible before things get locked in place. | ||
+ | |||
+ | Lionel had some questions about progress on single-page applications based on the VuFind API. Demian is not aware of further work being done in this area. He noted that the existing VuFind API should be able to support a fairly robust search-oriented SPA, but significant additional work is needed to support additional features like user functionality (since authentication would need to be implemented). | ||
===== Next Call ===== | ===== Next Call ===== | ||
Line 53: | Line 68: | ||
---- struct data ---- | ---- struct data ---- | ||
+ | properties.Page Owner : | ||
---- | ---- | ||
community_call/minutes20220503.1651582845.txt.gz · Last modified: 2022/05/03 13:00 by demiankatz