Transcript Slide 1

University of Wollongong
EQUELLA Implementation
using a replicated datastore
1
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
o Subject resources
 Faculty based
 75% of total items
 Workflow to QA media files
o Research resources
 Faculty based
o Share World
 Harvested through Content Without Borders
o Share UOW
 Central UOW units
2
3
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
4
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
5
RDS – users, groups and roles
• Security manager >
User Management >
Replicated datastore
6
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
7
EqMS - Groups
• ITS managed groups and users
• Extension group mapping
• Extension group - manual
8
EqMS - Users
Student user, ITS managed
Staff user, ITS managed
Test account, extension user
Student user, ITS managed
9
Test account, extension user
EqMS
• Audit logs
10
Usage - Item Metadata ACL’s
Resource access – unit only
Law
11
Case Study – Faculty re-alignment
New faculty structure
12
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).
Parent_Group_ID
Child_Group_ID
Child_Group_Name
FACULTY_25 ( LHA)
FACULTY_25
FACULTY_25
FACULTY_25
FACULTY_25
FACULTY_25
UNIT_14
UNIT_110
UNIT_86
UNIT_111
UNIT_87
UNIT_88
Arts
Indigenous Studies
English Literatures and Philosophy
Language Centre
History and Politics
Social Sciences, Media and Communication
FACULTY_25
UNIT_44
Law
Previous Faculty, now school
FACULTY_25
UNIT_10
Creative Arts
Previous Faculty, now school
Staff user in LAW > ALESCO/WFACLHA243 > UNIT_44
13
Case Study – Faculty re-alignment
•
All user / group relationships were managed from RDS, no further work
was required in EQUELLA
•
Work required in EQUELLA
o Collections: scripting item metadata ACLS, change UNIT names
o Manage existing items: bulk move to new faculty if required
o Bulk update existing items: subject taxonomy, change faculty name
•
14
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)
15
Future – Schools realignment
• Review of schools within new faculty structure
• Final structure consists of
o Creation of new schools
o Deletion of some existing schools
o 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
16