The Course data project includes\u00a0 both the Course Data Synchronisation and KIS work packages which have been delivered under a programme of work for Stage 2.\u00a0 Below is an update from those involved in the delivery this key work.<\/p>\n
Course Data Synch – <\/strong>(Course and Module Design Tool) For information, we have had some terminology changes since delivering this work that involves changing our terminology from Programmes and Courses to to Courses and Modules.\u00a0 This meets with KIS and NSS standards.\u00a0 I have gone through the text and changed the wording … and hope I’ve amended correctly.<\/p>\n The work here involved moving Course and Module data back from the Curriculum Planning tables back into the main oracle tables (these are our current integrated student system and course\/module system).<\/p>\n The Course and module design tool was used to amend or create any course or module to run in the 2012 academic year, and in particular to certify that Course learning outcomes were fulfilled by a Module in that course and Module learning outcomes were tested by assessment.\u00a0 This system supported the Insitutional Curriculum Review process, which has standardised the credit volume attributed to courses.\u00a0 The main Course and Module management Oracle forms needed updating to support these changes, plus the change to the structure of the academic year.\u00a0 A data migration working group met weekly to discuss and resolve any issues arising.<\/p>\n Oracle forms were developed to enable Academic Registry staff to undertake the migration, on a school and department basis as necessary, and tested thoroughly and bug fixed using data from the Law, Politics and Sociology School and Engineering and Informatics.\u00a0 Once each school was ready their Course and module data within the design tool\u00a0 was given a status of \u2018Ready to Migrate\u2019.\u00a0 All existing modules were end dated on the database, then the School by School migration process created new versions of modules using the data from the Course and Module Design tool ready for the 2012\/13 academic year.\u00a0 The next step was to copy back the 2012 versions of modules to the 2011 and 2010 cohorts, so that all students are taking the same versions of modules with the correct number of credits.<\/p>\n Key Information Sets – KIS<\/strong><\/p>\n A KIS Operational Group was created to provide co-ordination and management of the operational aspects to KIS preparation at Sussex, including oversight of management information, student systems, IT infrastructure and communications.\u00a0 It has met twice so far and reports to the Strategic Data Reporting, Optimisation and Forecasting Group which is responsible for the strategic aspects of KIS.\u00a0 As this is the first year of the KIS, and due to the Curriculum Review – Sussex will be presenting a estimate of key statistics rather reporting on existing data.<\/p>\n Database tables to hold the KIS data have been created and oracle forms have been updated to enable maintenance of the KIS data associated with courses and modules.\u00a0 KIS types have been identified and scripts written to populate these attributes.\u00a0 The process is being led by members of the Governance team who has worked with other stakeholders to identify how related data will be provided \u2013 for example Residences, Careers and Employability.\u00a0 The XML schema for the delivery of the KIS data is available from HESA, who are collecting the data returns this year.<\/p>\n","protected":false},"excerpt":{"rendered":" The Course data project includes\u00a0 both the Course Data Synchronisation and KIS work packages which have been delivered under a programme of work for Stage 2.\u00a0 Below is an update from those involved in the delivery this key work. Course Data Synch – (Course and Module Design Tool) For information, we have had some terminology […]<\/p>\n","protected":false},"author":45,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[175],"tags":[195,205,194],"_links":{"self":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts\/38"}],"collection":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/users\/45"}],"replies":[{"embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/comments?post=38"}],"version-history":[{"count":8,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts\/38\/revisions"}],"predecessor-version":[{"id":72,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/posts\/38\/revisions\/72"}],"wp:attachment":[{"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/media?parent=38"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/categories?post=38"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blogs.sussex.ac.uk\/coursedata\/wp-json\/wp\/v2\/tags?post=38"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
\n<\/strong><\/p>\n