...
- Time: 9:00am PDT / Noon EDT
ZOOM connection: https://notredame.zoom.us/j/94030214208
(link will launch Zoom client – if you do not have Zoom, expand the instructions below)Expand title Click to view telephone/H.323/SIP connection instructions Meeting ID: 940 3021 4208
One tap mobile
- +13017158592,,94030214208# US (Germantown)
- +13126266799,,94030214208# US (Chicago)
Dial by your location
- +1 301 715 8592 US (Germantown)
- +1 312 626 6799 US (Chicago)
- +1 646 558 8656 US (New York)
- +1 253 215 8782 US (Tacoma)
- +1 346 248 7799 US (Houston)
- +1 669 900 6833 US (San Jose)
Meeting ID: 940 3021 4208
Find your local number: https://notredame.zoom.us/u/aPls29JbL
Join by SIP 94030214208@zoomcrc.com
Join by H.323
- 162.255.37.11 (US West)
- 162.255.36.11 (US East)
- 115.114.131.7 (India Mumbai)
- 115.114.115.7 (India Hyderabad)
- 213.19.144.110 (EMEA)
- 103.122.166.55 (Australia)
- 64.211.144.160 (Brazil)
- 69.174.57.160 (Canada)
- 207.226.132.110 (Japan)
Meeting ID: 940 3021 4208
Agenda
(meeting notes below)
...
- Ryan Wick (Oregon State University)
- Juliet Hardesty (Indiana University)
- Rob Kaufman (Notch8)
- Thomas Scherz (University of Cincinnati)
...
Meeting Process
...
- Community Vocabulary Manager (Julie)
- Ryan Wick and Julie are drafting a functional requirements document
- Much of this comes from the metadata interest group
- Most immediate need: set of Hyrax-specific predicates need to be resolvable from real URIs
- Currently the URIs resolve to an invalid namespace
- There are three scripts which work directly with these
- These are going to continue to be hosted by the fake namespace
- Perhaps approaching the updates for these scripts could be an initial step?
- PCDM and fcrepo ontologies
- These are human-readable, but machine-readable should be preferred
- Contemplating creating a GitHub repository
- If GitHub Pages is used, leveraging this might be possible
- Perhaps vocabulary.samvera.org could be reserved by Heather for the Samvera Community
- If this is the case, perhaps the repository should be created within the samvera-labs Organization
- Property proposals
- Pull requests for individual properties is preferred for this approach
- Otherwise, coordinating this with multiple properties could make reviewing difficult
- Merging pull requests should the trigger a rebuilding and republishing of the site
- Property proposals
- Multiple Repositories for Samvera URIs
- hydra-works (and perhaps others) have hard-coded URIs
- These must be replaced
- hydra-works (and perhaps others) have hard-coded URIs
- Should this just be deployed to the samvera GitHub Organization?
- Perhaps still test this from within the samvera-labs Organization?