About Features Downloads Getting Started Documentation Events Support GitHub

Love VuFind®? Consider becoming a financial supporter. Your support helps build a better VuFind®!

Site Tools


Warning: This page has not been updated in over over a year and may be outdated or deprecated.
community:pmc_meetings:minutes20220214

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
community:pmc_meetings:minutes20220214 [2022/02/14 14:59] – [PMC Meeting: February 14, 2022] demiankatzcommunity:pmc_meetings:minutes20220214 [2022/02/14 16:32] (current) – [8. OLF Update] demiankatz
Line 1: Line 1:
 ====== PMC Meeting: February 14, 2022 ====== ====== PMC Meeting: February 14, 2022 ======
  
-:!: This document is currently a draft and will be finalized as minutes following the meeting. +Attending: Oliver Goldschmidt, Leila Gonzales, Chris Hallberg, Demian Katz, Ere Maijala, Craig Murdoch, Mohan Pradhan, Hajo Seng
- +
-Attending: Leila Gonzales, Chris Hallberg, Demian Katz, Mohan Pradhan+
  
 Apologies: André Lahmann, Leander Seige Apologies: André Lahmann, Leander Seige
Line 25: Line 23:
 Leila posted [[community:surveys_and_statistics:understanding_discovery_platform_usage_survey_2021|results on the wiki]]. Leila posted [[community:surveys_and_statistics:understanding_discovery_platform_usage_survey_2021|results on the wiki]].
  
-This seems to support the value of ongoing investigations related to authority data.+This seems to support the value of ongoing investigations related to authority data. Possible action: discuss on Community Call (May?). Ere highlighted the complexity of dealing with authority data from multiple sources. 
 ===== 3. WOLFcon 2022 ===== ===== 3. WOLFcon 2022 =====
  
 +Hajo attended the first program planning meeting for WOLFcon. Time slots are fixed in place and room size/availability is known. The FOLIO community is developing a lot of content. We should determine as soon as possible what VuFind content we want to present.
 +
 +Format expected to be hybrid but with strong in-person component.
 +
 +Hajo will share details of schedule so we can plan further.
 +
 +There is an opportunity for some hands-on workshops to show ease of installation/use of VuFind.
 +
 +Hajo has been discussing the possibility of a VuFind-specific social event as well.
 ===== 4. Improve VuFind Installation List ===== ===== 4. Improve VuFind Installation List =====
  
Line 34: Line 42:
 Other remaining actions: Other remaining actions:
  
-  * Decide which email address(es) the form should notify +  * Decide which email address(es) the form should notify (Demian and Chris for now; PMC forwarding address a possibility for the future) 
-  * Link to the form from the [[community:installations|installation list]] itself.+  * Link to the form from the [[community:installations|installation list]] itself. Demian will add this.
  
 ===== 5. vufind.org Web Analytics ===== ===== 5. vufind.org Web Analytics =====
  
 As discussed last month, Demian did some very minimal analysis of the top 40 web pages on vufind.org, finding that all of the frequently-accessed pages also seem to be reasonably up to date. The page that probably is most in need of attention is [[indexing:open_data_sources|open data sources]], which contains a lot of information that hasn't been checked in close to a decade (though it also includes some current and useful things). Perhaps we should consider breaking this into smaller pieces and/or reviewing all of it. As discussed last month, Demian did some very minimal analysis of the top 40 web pages on vufind.org, finding that all of the frequently-accessed pages also seem to be reasonably up to date. The page that probably is most in need of attention is [[indexing:open_data_sources|open data sources]], which contains a lot of information that hasn't been checked in close to a decade (though it also includes some current and useful things). Perhaps we should consider breaking this into smaller pieces and/or reviewing all of it.
 +
 +General consensus: if we want to keep all the content, split it into multiple levels -- "hub" pages for types of data (authority/bib/linked/etc.), with lower-level pages containing specific examples. Move XSLT examples into the code base (when appropriate) instead of keeping them inline in the wiki.
 +
 +Before splitting content, review what is still working/relevant. If we can/should delete most of the content, maybe reformatting is less relevant.
 +
 +Another possibility to consider: using the [[https://www.dokuwiki.org/plugin:folded|Folded]] plugin to collapse some of the content.
 +
 +Demian will review when time permits and share ideas next time.
 ===== 6. GitHub Branch Protection ===== ===== 6. GitHub Branch Protection =====
  
Line 46: Line 62:
 ===== 7. Documentation ===== ===== 7. Documentation =====
  
 +No news this month.
 ===== 8. OLF Update ===== ===== 8. OLF Update =====
  
Line 52: Line 69:
 Additionally, VuFind has been assigned three votes for the current open seat on the OLF roundtable. We should determine a process for allocating these. Additionally, VuFind has been assigned three votes for the current open seat on the OLF roundtable. We should determine a process for allocating these.
  
 +Decision: give votes to PMC members who are also OLF officers (manager/secretary/treasurer); discuss at PMC meeting prior to voting so that full PMC can share input with these representatives.
 ===== 9. Release Planning ===== ===== 9. Release Planning =====
  
Line 57: Line 75:
  
 Demian also raised the possibility of 8.1 and 9.0 releases coming closer together than in the past -- the work on both releases is tied together by the new theme, and they may end up being ready at closer to the same time than we have seen in the past. Demian also raised the possibility of 8.1 and 9.0 releases coming closer together than in the past -- the work on both releases is tied together by the new theme, and they may end up being ready at closer to the same time than we have seen in the past.
 +
 +Send round-up of outstanding theme-related PRs to PMC for final review as needed.
 ===== 10. It Takes a Village: Resources Module ===== ===== 10. It Takes a Village: Resources Module =====
  
 Following last month's PMC activity, Craig drafted a [[https://docs.google.com/document/d/1ur96HJXsQeQ806UnfluGuc9syM77QmMP3_EEdlJEqyc/edit?usp=sharing|Registered Service Provider Agreement]] for further discussion. Following last month's PMC activity, Craig drafted a [[https://docs.google.com/document/d/1ur96HJXsQeQ806UnfluGuc9syM77QmMP3_EEdlJEqyc/edit?usp=sharing|Registered Service Provider Agreement]] for further discussion.
 +
 +There was some discussion about the need to clarify benefits and obligations in the RSP document. It may be helpful to "lead with the benefits" (maybe move the table from the bottom to the top).
 +
 +Question: should listed service providers have a separate agreement? Regardless of answer, RSP document should probably be more clearly geared toward RSPs -- we can use LSPs as a point of comparison but they should have a separate agreement (if we want them to sign something at all).
 +
 +Side discussion: we should set up rules for ensuring that LSPs remain current -- i.e. request regular contact to keep list up to date; remove if no contact after X amount of time.
  
 The "new forms of community engagement" activity at the February Community Call also generated some ideas; Demian will follow up at the March Community Call. The "new forms of community engagement" activity at the February Community Call also generated some ideas; Demian will follow up at the March Community Call.
Line 80: Line 106:
 ===== Other Items ===== ===== Other Items =====
  
-===== Action Items =====+Mohan reported progress on setting up services to support VuFind members.
  
 +===== Action Items =====
  
 +  * Demian: Continue moving OLF membership process forward.
 +  * Demian: include authority data discussion on a future Community Call agenda.
 +  * Hajo: share WOLFcon schedule details with the PMC to support further planning.
 +  * Demian: set up instance report form to email to Chris; link to form from installation list.
 +  * Demian: review Open Data Sources wiki page and develop proposals for discussion next time.
 +  * Demian: share voting links (and personal opinions, if any) with OLF officers.
 +  * Demian: send summary of outstanding theme-related pull requests to PMC members for final review.
 +  * ALL: review the draft Registered Service Provider Agreement and leave comments for deeper discussion next time.
 ---- struct data ---- ---- struct data ----
 +properties.Page Owner : 
 ---- ----
  
community/pmc_meetings/minutes20220214.1644850768.txt.gz · Last modified: 2022/02/14 14:59 by demiankatz