...
| Time | Item | Who | Notes |
|---|---|---|---|
| Introductions | |||
| History | Sufia - documentation https://drive.google.com/drive/folders/1AvxAVFusdFBjgKU3HD64mcp8jcElelKc?usp=sharing DSpace to Sufia - missing Collections - display set wg, came to be CE WG - Lynette picked up and Collections Extension is almost finished Not just data but features are missing - some features are missing - UM wants to see what features are important and how we're doing data migration Hoping to get folks who've migrated like SVT Josh Gum from OSU - want to hear Josh's experience | ||
| Who is done with migrations? | Josh - repairing metadata and migrating it over to appropriate admin sets, for example - lot of DSPace db queries. get an idea of state of data - launching big effort. Discovering metadata issues before and after migration - querying DSpace now to check back in unocvering metadata quality issues Benefits in how we migrated - hdl issued to DSPace - have that key in index - query for hdls - those are things that come from DSPace - no handle in Hyrax Lot of work types 8 or 10 different types - 11 admin sets A dozen admin sets can have literally any combination - all relative to pre-work of db analysis, of type sof works in DSpace. Sub-collections - those mostly mapped to work types and admin sets we'd designed. 400 collections - many of them were the same - Biggest were ETDS. Easy to identify what could be processed as ETDs. Other works all needed to be evaluated. They belong in the Article Admin set (ex). | ||