ScholarWorks : 2019-05-16 Meeting notes

15m

Updates from previous meeting

David
Kevin

• Production system update

  • authentication

    • Fullerton and Sacramento working

    • Dominguez Hills into prod (date TBD)

  • models, admin set

    • Recommended models from dev to prod

    • Just the last bits of set-up today

    • Kevin will send out email so folks can start testing on prod

• Demo system will be upgraded to Hyrax 2.5

  • for accessibility review by UI task force

• Workflows

  • Three-step process – Kevin exploring

  • Admin sets – based on above

• Thesis committee member authorities – won’t pursue at this time.

• Rights statement missing in interface – to UI task force

• Bibliographic citation – to Metadata task force

• Copy-paste bug in abstract – Kevin exploring

25m

Report on testing & questions

Dana
Bin
Mark

• Dominguez Hills

  • Control over fields

    • How date fields should be formatted?

    • No drop-downs for certain controlled fields

      • Degree level

    • To Metadata task force

  • Batch uploading process

    • Not obvious how this works

      • Dana will write-up documentation on this

      • Only allows audio-visual format type

    • Would like one that works more like DSpace today

      • Dominguez Hills has developed workaround

  • Department field

    • Shows up in lower case on the public side

• Fullerton

  • Preliminary testing so far, not uploaded yet

  • Inviting some others to do more testing after end of semester

  • New OER librarian coming on board soon

  • Date

    • Nice to have a calendar or something

  • Department list

    • Kevin will double-check to make sure this has been added to

  • Cannot add ETDs

    • Kevin and David will check

  • Where to put institutional documents (academic senate, syllabi)?

    • Implementation Team

  • User role management?

    • In production, anyone who authenticates gets shunted into groups

      • Campus group set

      • Other groups based on attributes

      • Still getting campuses on-board with authentication

    • We will need to go over this once we finalize a few things

• Sacramento

  • Data migration

    • Required fields in form does not impact this

    • Existing fields in DSpace should be mapped correctly to the fields in Hyrax

    • Data review phase should address this

    • Embargoes would be set to private

  • Batch-upload

    • Always shunts you into an ETD model

    • Add New Works by Batch options:

      1. Each file will be uploaded to a separate new work resulting in one work per uploaded file.

      2. To create a single work for all the files, go to Add New Work

      3. You can add one or more files to associate with this work. - False; batch uploading creates a separate record for each file

      • The first and third statements seem to contradict each other. The form creates a separate record for each file.

  • Review works submitted by users

    • No option to edit metadata, either in review or afterward

20m

Future steps

David

• New documentation derived initially from Kevin’s original orientation document.

  • One document preferred vs. many

  • How best to document the data dictionary?

    • Metadata fields

    • Form elements required vs. not