...
Attendees
Bin Zhang
Discussion items
Time | Item | Who | Notes | |||||||
|---|---|---|---|---|---|---|---|---|---|---|
Monthly updates5 min | SWAT team | David Walker Kevin Cloud (Unlicensed) |
| SWAT team |
| OJS | Test server up and running Discussion around authentication, branding, plugins, other considerations Final data migration Clone, and move to production
| Looking into and evaluating cost/benefit of multiple instances vs. one instance. Historically COLD not as involved with SW Hasn’t been serious consideration and conversation about the resources needed to do what we want to do with an IR Delays (turnover and staffing) aren’t new but reflect that we are under-resourced Now is the time to come back to SW and reexamine what we need, including looking at what we really need--what the priorities are TF will look at whether we really need separate instances or if there is a better deployment model with one instance and then sep collections, staffing considerations, what are the costs associated with these things? COLD created a SWAT team to look at these issues (Oct 5 is deadline for nominations) Expected to provide report in Dec with final rec in Feb Also looking into implementation, doesn’t change what we are trying to achieve, we’re carrying those forward. Impact is post-migration, how we are going to implement No option has been taken off the table, more exploration of what are the costs associated with the options and what resources are needed to move those options forward | ||
5 min | OJS | David Walker Kevin Cloud | Test instance of OJS up and running Interest has gotten to the point where we need to really support OJS DW has test instance up and running (latest version of OJS with data from our ‘Beta’ OJS) Now migrating PUMP into the test instance into our test OJS this will have implications for other campus one-off OJS journals as they come and ask to be hosted on our OJS What are needs around authentication, plug-ins, branding. After this, then a final migration to the test server, and then clone to make a new production server. Then get rid of all test journals on the production site. Production will be nothing but production and close-to-production journals. At that point close down the beta server and it will point to the new server Timeline for the next month to have completed the production server In the future migrating journals from other places (DSpace, for instance) to OJS One of the challenges we’ll face is that CO is providing all the tech support and so we need mechanism to teach people how to use OJS | |||||||
5 min | Updates from Kevin | Kevin Cloud | Completed first pass migration for Sac State, investigating Hyrax middleware called Valkyrie, may be core component, could expedite a bit of our processing, a way to leverage diff technologies to speed up the process. KC will be at Samvera Connect and expects a lot of convo on Valkyrie Will pick up migrations for DSpace content perhaps using it Working to get implementation together for CSUSM production site Goal to keep it moving forward because it will impact all campuses Self-deposit form creation is in works Demo sites available to do more onboarding (eventually) to familiarize us with the platform and what options we have. Help us understand Hyrax and how it differs from DSpace What the linked data looks like and what it means for system resources | |||||||
2 min | Metadata/Linked Data | Lauren Magnuson | Metadata/Linked Data Charter Draft (Final) and 2018-2019 Projects (Lauren) Four projects for the year If there are comments, questions, feedback, let Lauren know | |||||||
2 min | Trusted Repositories | Andrew Weiss | Create a spreadsheet of best practices criteria, will be coming in the next few weeks |