University of Wollongong

1. University of Wollongong EQUELLA Implementation using a replicated datastore

2. UOW EQUELLA Implementation • In transition from Vista eLearning to Moodle, using EQUELLA for resource management • No bulk migration, favoured on-demand quality resource migration assistance • Collections • Subject resources • Faculty based • 75% of total items • Workflow to QA media files • Research resources • Faculty based • Share World • Harvested through Content Without Borders • Share UOW • Central UOW units

4. UOW EQUELLA Implementation Usage RDS – users, groups and roles RDS – subject taxonomy EqMS – custom built web application for interface to RDS Example – Item metadata ACL’s based on owner’s groups determine resource access Benefits Case study – Faculty restructure Case Study – GSM institution merge Future – Schools realignment

5. RDS – users, groups and roles No internal EQUELLA users, groups or roles All users, groups and roles are managed using EqMS (EQUELLA Management System) as the interface to the RDS Data source of RDS is ALESCO HR system, where Clevels are mapped to faculties and units in UOW Parent / child hierarchy for faculties and units

6. RDS – users, groups and roles Security manager > User Management > Replicated datastore

7. RDS – Subject taxonomy • Subject taxonomy is a direct data feed from subject database • Get term select term, fullterm, isleaf from taxonomy_terms where fullterm = :term and taxonomy_id = -1

8. EqMS - Groups ITS managed groups and users Extension group mapping Extension group - manual

9. EqMS - Users Student user, ITS managed Staff user, ITS managed Test account, extension user Student user, ITS managed Test account, extension user

10. EqMS Audit logs

11. Usage - Item Metadata ACL’s Law Resource access – unit only

12. Case Study – Faculty re-alignment New faculty structure

13. Case Study – Faculty re-alignment • All user data was automatically realigned to new Clevels in ALESCO • In EQUELLA RDS, new mapping of Clevels to units and faculties using parent/child hierarchies • For example, 3 faculties were combined into a new faculty called Law, Humanities and the Arts (Faculty_25). Staff user in LAW > ALESCO/WFACLHA243 > UNIT_44

14. Case Study – Faculty re-alignment • All user / group relationships were managed from RDS, no further work was required in EQUELLA • Work required in EQUELLA • Collections: scripting item metadata ACLS, change UNIT names • Manage existing items: bulk move to new faculty if required • Bulk update existing items: subject taxonomy, change faculty name

15. Case Study – GSM Merge A separate EQUELLA institution at UOW existed for GSM GSM has separate schemas, collections, items On transition to Moodle, business decision to merge GSM institution with UOW institution GSM users already existed in UOW RDS As part of the faculty realignment, new Clevels and mapping to new unit under new faculty Science, Medicine and Health ACL Users with staff role AND NOT Graduate School of Medicine (UNIT_93)

16. Future – Schools realignment • Review of schools within new faculty structure • Final structure consists of • Creation of new schools • Deletion of some existing schools • Transferring of some schools to other faculties • Same process as the faculty re-alignment where majority of work is done by automatic data feed to RDS