Date: 10-10-18

Time: 12:30-2:30pm MTN; 2:30-4:30 EST; 11:30am-1:30pm PST

Location: Rm 1715 and remote participation

Join from PC, Mac, Linux, iOS or Android: https://unc.zoom.us/j/712530628

Or iPhone one-tap :
US: +16699006833,,712530628# or +19294362866,,712530628#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 669 900 6833 or +1 929 436 2866
Meeting ID: 712 530 628

Agenda:

-Discoverability in Hyrax: Repo-managers discoverability subgroup

-What do we want to do over the next year?

-How do we interject our institution needs on the Hyrax roadmap

add topics here please!

Attendees: Please note if you will be online or in person

jrudder - in person

susan borda - remote - I can make it from 3:30-4:30

Hui Zhang - remote

Gabriela Montoya - remote

Moira Downey (Deactivated) - in person

Hannah Frost - in person

Sherry Lake - in person

Nabeela Jaffer - in person

Emily Porter - in person

Will Sexton (old account) - in person

Notes:

Topic #1: What to do over the next year?

Used to have monthly meetings, with show & tells, that would be useful
Work types - form a working group?
Spin out small working group with metadata group, talk about what the default work group needs are, what fields do they need to have?
Messaging - send an email every month that a meeting is coming up. Instead of just posting on slack channel
Subscribe to Google groups - lots of activity there to monitor
Give input on the road map - Nabeela is on the Road Map Council now. Think about how to impact that group. If they share their agendas in advance, see if RMIG can have an impact.
Question about what the group does to have an impact on Hyrax development or other solution bundles. It’s generally kind of ad hoc and caught up in the churn. Discoverability is a more formalized effort.

But also Hyrax is starting to get a roadmap in place, and this group has had a voice in it.

Maybe do a webinar.
Any research-data-specific goals for the year? There is a group for research data. Michigan and Indiana will be collaborating, with Duke interested.
Do some auditing. Example, discoverability with Google Scholar. But not until Google is more transparent about discoverability for data repositories.
Lot of implication for articles in Hyrax, little things that we don’t quite know about.
Observation that some features have been poorly implemented in Hyrax, with little understanding of how they’d work on the service side. Example, embargo. Seems like service is not as involved as it should be.

Create a table listing features that are poorly done, and then how people have dealt with it.

Difficulty of giving code back to core. Examples Michigan - ordered metadata and tombstones. Willing to give code back, but how to push it through the process.

Collaborate with the HWG on a process for making these decisions.
Maybe the Roadmap Council could help with this discussion.
SIGHAR kind of works on priorities at higher level
All agree that this is a worthwhile thing to do

Production Hyrax repositories:

OSU (IR): https://ir.library.oregonstate.edu/
Northwestern (IR): https://arch.library.northwestern.edu
Michigan (data): https://deepblue.lib.umich.edu/data
Duke (data): https://research.repository.duke.edu

Browser not supported