There has been some discussion of tools and languages that haven't been part of the "standard" Samvera technology stack, including Elixir, Go, ElasticSearch, and others. What would be the most productive way to experiment with these? What are the pain points in most need of updating? Are there some parts of the stack that are less-entangled with the rest of the tools, making it easier to swap in new tools? Are there some languages that more Samvera organizations would be willing to adopt? Are there other concerns for where we should focus our exploration?
No bio.
The Permissioning Analysis Working Group produced recommendations that were supposed to be taken to developers in phase 2 of the WG for an investigation into the feasibility of the recommendations and potentially a proposal for how to get there with what is deemed feasible. That phase 2 work got stalled for various reasons. I would like to invite interested folks to reconvene and discuss next steps and to hear what permissions work is taking place in various institutions.
No bio.
Samvera Connect 2019 meeting of the Samvera Metadata Interest Group. Thursday, 10/24, 4:00-5:00pm. Agenda
No bio.
This session is to gather those interested in including more controlled vocabulary options for Keyword and Subject fields by default in Hyrax. We can talk in more detail about vocabulary options that are available. We'll also talk community approaches and technical approaches and see if this indicates the need for a Samvera working group.
Metadata Analyst at Indiana University. Metadata SME (subject matter expert) for Avalon Media System. All about the SMIG (Samvera Metadata Interest Group) and its working groups.
This is a follow-up for those interested in further discussion or information sharing to the presentation at 3 pm on Thursday. We are thinking of this session for 4 - 4:30 pm on Thursday.
No bio.
Could Samvera be expressed as a set of one or more API specifications? If so, what would those specifications encompass?
Existing products like Hyrax, Hyku, and possibly Avalon, would be reference implementations of these specifications. The end goal would be to enable someone to build a "Samvera application" that is compatible at an API-level with Hyrax/Hyku, etc. yet choose whichever technology stack they desire.
What we would accomplish in this session is to decide the answers to the above questions. If the answer is no, that's fine, we can document it and move on. If the answer is yes, and we want to pursue such an end goal, we can strategize how we might achieve this.
No bio.
Join us for a code read and a look at what you need to know to start exploring Wings. Bring your questions and curiosity.
This is a session proposed by SIGAHR (Samvera Interest Group for Advising the Hyrax Roadmap) to continue discussion about the road map, the Hyrax-focused working groups, the Product Owner role, all of that. See the SIGAHR wiki for the latest meetings notes and proposals regarding this work.
Metadata Analyst at Indiana University. Metadata SME (subject matter expert) for Avalon Media System. All about the SMIG (Samvera Metadata Interest Group) and its working groups.
We tried a few new things with the program this year (keynote speaker, lightning talks during poster session, closing plenary). What do we think so far of how those things went? What might we want to try next year? How is the balance of talks to breakouts? Should next year's date proximity to Halloween prompt us to make any particular adjustments?
Come with your feedback and ideas!
No bio.
We've done Deployment & Cloud Interest Groups in the past, but maybe it's time for a real Working Group. Our deliverables would include real shared things including but not limited to:
Tech Lead for Northwestern University Library's Repository & Digital Curation development team.
What kind of performance can I expect to get out of my Hyrax app?
What can I do to make my Hyrax app run faster?
This can be hard to answer, which in turn, makes project planning harder.
If we share some basic benchmarks, we can compare results, and have better expectations.
WGBH Boston
"afred" on Samvera Slack channel.
This is a chance to get together with Valkyrie implementors and ask questions or discuss the future features of the library. Interested in using Valkyrie? Want to know how we solve some problems? Have a feature or something you'd like to see? Come ask!
No bio.
The goal of this session is to revive the work of the Hyrax Analytics Working Group, using the following prompts:
link
What questions do you need repository analytics to answer for you?
What elements of development are most important to you ?
Minimally, what do repository analytics look like?
What do feature-perfect repository analytics look like?
What do institutional repository analytics look like vs. what cultural heritage repository analytics look like?