2020-02-04 Meeting notes

Date

Feb 3, 2020

Participants

  • @Carmen Mitchell (Unlicensed)

  • @David Walker

  • @Elizabeth Altman (Unlicensed)

  • @Elyse Fox (Unlicensed)

  • @Kevin Cloud (Unlicensed)

  • @Lana Wood (Unlicensed)

  • @Mark Bilby (Unlicensed)

  • @Patrick Newell (Unlicensed)

  • @Steve Kutay (Unlicensed)

 

Goals

Discussion topics

Time

Item

Presenter

Notes

Time

Item

Presenter

Notes

15 minutes

Updates on ScholarWorks /Campus 1-on-1 meetings

@David Walker

@Kevin Cloud (Unlicensed)

  • Full report tabled to next meeting.

  • Discussion of local accessibility requirements during the 1-on-1 meetings

    • Legal responsibility to have these materials be ADA compliant; need a better understanding of local campus practices for ensuring ADA compliance in IR works


15 minutes

Update from Metadata Working Group

@Elyse Fox (Unlicensed)

  • Review/finalize data dictionary on Confluence site; set deadline to complete by March meeting

  • Reviewing Rights stmt URI, identifiers survey (closes 2/7)

    • End goal is to have a drop-down with identifier

  • Reviewing subject access survey (closes 2/19)

    • Looking into group’s preferences/ opinions for keeping subject access at all when Hyrax is keyword searchable

15 minutes

Update from Digital Archives Working Group

@Steve Kutay (Unlicensed)

  • Repository Personnel Registry

    • Hope is to get a better understanding of campus projects and who is responsible for which components

    • Discussion of best way to communicate with designated personnel - send to the main contact or have separate lists by function?

      • Suggestion to copy the designated project point person in emails

      • Suggestion to allow each campus to put in who they want to be the designated point person for each functional group

      • Need procedure for updating / maintaining this list (annual review?)

      • Suggestion to have this live on the Confluence page

  • MWG/DAWG will have quarterly joint meetings and hold open ScholarWorks meeting reports for interest groups

  • Shared accessibility policies for digital reformats? Item level linking to policies?

    • Reach out to decision makers to consider how we want to maintain our guidelines (or best practices for sharing) regarding accessibility accommodations; particularly important given that some of the materials in an IR are being scanned from an analog form

  • Best practices for geographic access across CSU

15 minutes

Proposals from Metadata Working Group

@Elyse Fox (Unlicensed)

  • Seeking feedback on CSU-wide discipline faceting/taxonomy

    • MWG thinks using a controlled vocabulary of academic disciplines will be a nice way to connect the various campuses; MWG is seeking approval from the DRC to move forward with this project in Scholarworks

    • Questions

      • Does the CO have this type of information already?

      • What is the process for creating these discipline taxonomies?

      • How will this be a moving process given that names change; (forward and backward compatible) - need an easy way for campuses to request future taxonomies/categories

    • Approved by committee

  • Copyright/Rights Stmt/License FAQ page and contact(s) on SW landing page; MWG to survey campus current campus resources?

    • Who will field any copyright / rights questions? - Suggestion to link to the existing copyright first responders contact list so questions go to the specific campus contact

    • Discussion of previous responses to centralized copyright advice and decision to not have a generic list

 

DataCite

@Mark Bilby (Unlicensed)

  • Vote/census about whether the committee would recommend to COLD a consortial subscription to DataCite for DOI-minting?

    • Send comments/feedback to Mark via email before next meeting; will discuss at next meeting

Action items

Look into whether the CO has a master list of disciplines to be used for universal discipline taxonomies. @David Walker

Decisions

  1. Establish CSU-Wide faceting / taxonomy
  2. Repository Personnel Registry will live on the Confluence page