Posts Tagged ‘University of Exeter’

XCRI-CAP Quick Update

No Comments »

We recently had a meeting with our project team to discuss our progress with the XCRI-CAP mapping. It was important for us to finalise the fields that we will be feeding, enabling us to finish building our programme template in iPaMS. We found there were a few fields that didn’t quite map up between iPaMS and XCRI. An example of this was firstly the study mode field. In iPaMS we were holding a “modular” option whereas in XCRI there was an option titled “flexible”. We felt it was important to try and match up any of these inconsistencies to help make the feeding process as easy as possible. We have now changed our “modular” option to “flexible”.

Another field we discussed was the “assessment” field. Within iPaMS we hold a lot of data regarding assessment details, however, in this meeting we decided we would use our Marketing assessment field for the XCRI feed. This would be the same assessment information that would feed to our website, giving more concise information regarding the assessment. We also highlighted in this meeting that we needed to include not just the abbreviated version of the qualifications but also the full versions, such as Bachelor of Arts.

There were also a few fields we were unsure about, such as the “type” field held in XCRI. We weren’t sure exactly what information we could use for this field. The XCRI information explained that the “type” was for a grouping of similar courses in terms of target audience. We were therefore unsure whether to group them by discipline or by UG/PG. We contacted Alan Paull and he was very helpful in answering our questions. He explained that they have not published a classification or vocabulary for this element, except for CPD courses, so we could leave this element from our feed if we wanted. Alan also explained they were open to suggestions to how this might be handled. Has anyone else included this element in their feed, if so, let us know what information you are including.

After ironing out some of these issues we organised a meeting with the Marketing department for next week to go through our spreadsheet and talk further about XCRI. It is a very important aspect of this project and with the help from Marketing, it will allow us to market our programmes in the best way possible.

Once we have had our meeting with Marketing and finished updating our XCRI spreadsheet, we will pop it on the blog for you to all see. We look forward to finding out how everyone else has mapped their data so please send us links to your blogs.


Workflow Mapping

No Comments »

Workflow mapping and finalising exactly how we plan for programmes to be approved and amended within iPaMS has been an ongoing task since the start of the project.  Over the past few months specific meetings have been held where we mapped out Business Approval and processes that currently occur in SITS.  However our focus has been on programmes and making sure that the programme template is fit for purpose.  Therefore any conversation about workflow has been connected to this.  For example the Graduate School of Education (GSE) run a number of ‘Continuing Education Short Courses’.  We met with GSE to discuss how these would fit into the programme template.  These non-credit bearing programmes are in fact approved in module templates, thus we looked into the approval workflow of these to ensure that it maps against other processes within the system avoiding us having to build a separate element of workflow for this handful of programmes.

Now that we have stopped looking at programmes we have finished mapping the workflow processes.  Squeezed onto a page of A3 our workflow diagram is complicated, to put it mildly.  Consultation with Marketing and Faculty has confirmed when individuals need to receive notifications about different stages within the process and to who will receive these.  Consultation with Admissions and the Library has allowed us to streamline parts of the Business Approval process so that each department’s involvement occurs at a slightly different stage, improving communication and efficiency throughout the development of programmes.

We are currently organising meetings with colleges so that those involved in the design and amendment of programmes and modules can comment on the proposed processes and we can make sure that iPaMS will work at this college level.  There have been a few discrepancies between colleges so far, but these are only minor- for example some colleges have a Learning and Teaching Committee, others have Programme Approval Committees, Educational Strategy Group Meetings serve a slightly different purpose in some colleges…  However none of these factors affect how the process works within iPaMS.  All feedback, so far, has been very positive and it looks everybody is looking forward to iPaMS being finished and seeking the benefits of an online workflow process.


Programme Developments

No Comments »

Developments to the programme template have been ongoing over the past month.  As the TQA template has recently been changed it has taken until now for us to receive examples of how fields have been interpreted and the amount of information which has been entered into specific areas.  This has meant that we have had to do some ‘re-arrangement’ to the original template that we designed for iPaMS.  In light of these changes we have started to look at how our data will map against the XCRi-CAP feed.  While we do not plan to develop the actual feed until later in the project we identified only a few pieces of additional information required for XCRi and these have been simple to add into the programme template.  This means that hopefully there will be no changes needed to the template once we start adding more advanced functionality to the system.

Different versions of standard text have been defined for use in the TQA specification and our lead developer Helen has added functionality to the system relating these different text versions to descriptive fields such as the campus identifier.  This text can only be edited for the current academic year and will need to be ‘rolled forward’ for future years.  We have identified this as the most effective way to ensure that historic documents are archived effectively (with the correct version of standard text) and that consideration is given to factors such as developments on campus and any change of resources for each year.  Due to the nature of programme design it was difficult to define this text and the associated relationships.  For example there are a number of learning opportunities which are taught on different (or multiple) campuses and some which are validated by the University of Exeter, but are taught through collaborative provisions.  The need for flexibility in the template has made any standardisation difficult.

Beyond the progress that has been made within iPaMS itself there have also been some other developments in the project.  The faculty office has agreed to the simplified data format that will be used in the PDF output for the TQA specification.  This means that in the future it will be easier to change the information that is required for the TQA specification as using the current format would require specialised skills to edit the template due to the complexity of the code which would have been required to build this.

The web marketing team have started to look at how programme data will be displayed in different sections of the web service.  This was an important driver for the development of iPaMS, ensuring consistency in the way that data is displayed across all of the colleges.  Once this is complete we will be able to make any final assessments of the template before we start entering programme data from the colleges.


Progress to Date – May 2012

No Comments »

We have been working on the CRIATE project for five months now (not counting the work that started internally before the JISC funding) and we have achieved a lot: A full progress report is published on the Documentation tab above.

Our main achievements so far have been:

  • Module templates available for entering module data
  • College of Humanities’ (HUMS) 2012/13 module data entered and feeding to their intranet
  • College of Social Sciences and International Studies’ (SSIS) 2012/13 module data entered
  • College of Life and Environmental Sciences’ (CLES) 2011/12 and 2010/11 module data is nearly all entered
  • End users trained on iPaMS from HUMS, SSIS and CLES

The next month is going to be extremely busy for the project team. We are planning to:

  • Finalise and test the programme template for 2012/13 data
  • Start entering 2012/13 programme data for HUMS, SSIS and CLES
  • Migrate archive programme and module data from HUMS’s and SSIS’s old database
  • Finalise the design for a feed from iPaMS to our various institutional websites (for prospective and current students)
  • Continue designing the online workflow for programme and module approval

We are also planning for a pilot integration with SITS (later this summer). We are already able to display the module diet of a programme in iPaMS (sourced from SITS), but we also want to be able to push data into SITS from iPaMS. The pilot will most likely focus on module information, as this is relatively simple with little dependency on data from other sources. If it is successful, this will open the doors to more data flowing from iPaMS, which will help cut down on administrative tasks and the risk of mis-keying data.

Keep checking our blog, as we will update on each of the tasks above over the next few weeks.


Introduction

No Comments »

I’m Samantha Briggs, the new Programme Approval Officer in Academic Policy and Standards. I’m working closely with the iPaMS/CRIATE team at the moment, helping them to understand how our programme approval and amendment processes work, so these can be incorporated into the database.

I’m looking forward to being able to see the stage-by-stage development of new programmes though iPaMS/CRIATE, so I can work more closely with Colleges in making the University of Exeter’s programme and module documentation world-class, and to help our College staff tackle barriers in advance of submitting their paperwork for Stage 3 approval by the Dean of Taught Faculty.


Marketing Update

1 Comment »

The Marketing Team on the project team have been looking at how we are going to use the information stored in the iPaMs database, and making it fit for purpose.  The Marketing Team need to be able to confirm information at the earliest stages of development of a programme as we’re communicating with prospective students well in advance of programme start dates. We’re predominantly concerned with web pages for prospective students, but College Web Marketing Officers who are part of our wider team, will potentially be required to amend information published to current students: it’s the visibility of the website which often prompts the required change.

Key developments we are currently undertaking include:

  • Working on the Programme template, keeping in mind what we want to use the information for.  For example, we have suggested that we want a separate Marketing field to list the discipline area the programme falls into.  We discussed pulling the field from SITS, but it was decided that this doesn’t necessarily map onto our discipline/subject list, therefore is one is not fit for our purposes.  We are also keen to have a separate programme description field which we can amend to ensure the information follows our University style guidelines, and is suitable for a prospective student, as well as other audiences who may be seeking information on our website.
  • Amending and creating module descriptions which will be able to publish directly to the website.  In the 9k fee environment, it will be increasingly important for prospective students to know the details of what they will be studying.  Although we provide information at the moment, the iPaMs database will allow us to provide consistent information in a consistent format which can be easily understood by prospective students.  The amends can range from ensuring we are following the University-set style guidelines, to writing a new module description where none exists.  Currently the spreadsheet of modules has 903 modules from the College of Humanities and the College of Social Science and International Studies which have been added to iPaMs, but this is constantly growing as more modules are added by the team, and the colleges.

Programmes

No Comments »

The consultation period for the programme template is, at long last, complete.  The web developers can now start coding the fields that data will be entered into.  It has been a long and drawn out process ensuring that all future iPaMS users will be able to store all of the necessary information they require against each programme.

Trying to reduce the amount of duplicated information related to programmes has taken up a great deal of time within the consultation period.  In some instances, such as with the programme description, one narrative is required to provide information for the TQA specification, the prospective students and current students sections of the web service and within the undergraduate prospectus.  Traditionally text would feed from separate places to each individual source; iPaMS, as the definitive source of programme information will now hold all text relating to the description of the programme in two fields, this will not only help keep all of the information for each output current but will improve efficiencies in terms of less repetition.

A number of fields required within the TQA Specification will be automatically populated from information collected within other fields.  This again reduces the amount of duplicated information held against each programme and will improve efficiencies within the programme creation process.  Standardised text and links will also be created at college level so that these do not have to be replicated by different departments, the population of these will be determined on the responses given in other fields.

User access to programme fields has also been established.  This will mean that departments will be able to update any changes to programme information that is related to them; most of these changes will automatically feed to the web service and there will be no delay in waiting for this information to be edited in T4.

There are still a number of different areas relating to programmes which have not been defined, such as how they will be linked and whether some fields will push into/ pull from SITS; however now we have defined the fields which are required it will be easier to make a decision on these areas of functionality.


Linking Programmes

No Comments »

Whilst recently investigating programmes we have come across some previous templates holding multiple programme data, such as those that have the same programme content but give you the choice of receiving a BA or a BSc. Similarly we have also found 3 year programmes that allow the choice of an extra year for MSc to be held on the same template. Furthermore, programmes that enable an optional year abroad/placement have also been held on the same programme and instead should be held separately. The main focus of us separating these templates is due to the intricate workflow that is being developed and the fact that each programme needs to be approved separately.

duplicate small

Currently, as we have mentioned, many of these similar programmes have been held on the same template. Since Colleges will now have to split these programmes up we have been working on how to make the transfer of data between programmes easier. One simple idea is to have a “duplicate” button. This would either copy all the data across or specific chosen fields, from one programme template to another; the user would then delete/change any of the data to fit with the new programme. These are the simple ideas for programme linking but the downside of this approach is if the similar programmes needed editing, each programme would have to be edited individually.

parent small

The more complex process is following a parent-child idea. This allows one programme to be a “parent programme” allowing you to copy its data across to another programme. This is similar to the duplicate idea, however, when data is edited in the parent programme, the data would also change in the child programmes automatically. We have discussed, regarding the parent-child process, if any data was edited within the linked programmes that notifications would arise. These notifications would let the user know that this programme is linked to others. Further discussion to how the notifications would work and what they would display will be considered in more detail if this process was chosen.

We have been in discussions with everyone from the project team about these ideas and we are still working on what process would be best. The initial duplicate button is quick to develop and easy to use, however, it would expect users if editing, to edit all programmes individually. In comparison, the parent-child would be more complex to develop but would allow easy editing functions for users throughout all linked programmes.

Please comment and let us know what you think. What are you doing with your institution?


Project Update

No Comments »

Workflow with the Faculty Office

At the beginning of the week Cat, Sam and I met with Kate and Samantha from the faculty office. We were looking through stage 1 of the workflow which we had previously mapped out at the beginning of the year.  This meeting was very successful in working out what notifications faculty wanted and when they wanted them. It also helped to check the workflow was correct and what needed modifying. It was additionally decided that the faculty office would get their notifications within iPaMS rather than to a central faculty email. We currently still working on the workflow diagram and will be meeting with other departments to discuss their involvement in the workflow.

Lauren Welland (Project Support Officer)


Programmes

We have started to look at how programmes will be stored within iPaMS and which pieces of information we will need to hold against each specific programme.  The functionality of iPaMS has been a major consideration here as information from the programme specification will be used as a marketing tool for prospective students and as an information source for current students, it will hold all of the information required to comply with TQA and QAA standards and be worded in a way that will easily link in with the XCRI- CAP data feed.  Information imputed as a part of the workflow process for approving new programmes will also be archived against each specific programme, as will any changes made to the programme and the date in which these take effect.  Currently we have identified over 100 data entry fields for each programme; once we have established the level of data exchange between SITS and iPaMS this number could increase further.

Cat Hine (Project Support Officer)


User Roles

This week I have been working on assigning roles to users. I have first been creating different roles and permissions within iPaMS. Using Zend navigation I can hide/show relevant links dependent on the permissions these roles have. Some examples of roles will be system administrator, Webservice role and developer. I am also working on restricting view of data by College, to do this we are currently assigning all modules to their College. At the moment every iPaMS user has access to all the data in iPaMS, once we start moving other Colleges into the system we don’t want them to have access to edit other College’s data.

Ben Norcombe (Developer)


Code Improvement

I am currently rewriting the iPaMS module controllers. This builds on the work we did for the previous release of iPaMS to improve the codebase. That work was mainly about reducing the amount of SQL queries per page/action, whereas this time it is about cutting down on code repetition, thus creating reusable functions. The benefits will be that the iPaMS code is easier to maintain as well as more scaleable, setting us up nicely for work to begin on Programmes

Helen Connole (Lead Developer)


CLES Data

This week I have been working on collecting the CLES data needed for archiving into iPaMS. With help from the College we have collected a vast amount of word/pfd documents for their modules ranging from the academic years 08/09- 11/12. On Wednesday Sam, Cat and I met up with Andy, the Taught Programme Support Manager for CLES and discussed iPaMS. It was a very successful meeting where we showed iPaMS in action and discussed the move of CLES data onto the system.  As CLES’ data is all on word/pdf, a move to the database should help them significantly with reporting information and having easier access to their data.

Lauren Welland (Project Support Officer)


Module Templates

No Comments »

One part of the project we are focusing on at the moment is to start archiving module data. To be able to do this we need all the descriptor templates that have been used over the previous years, to be created in iPaMS. With help from the faculty office we have located all seven of these descriptors. With agreement from the project board we will initially be working on archiving only data up to 08/09, however we have worked on adding older module descriptors in case we need to archive further back.

So far in iPaMS we have 3 module descriptors. First is the new 12/13 module descriptor which Humanities have been working on for their new module data. The second descriptor is known as the “DWAiPaMS” descriptor. As mentioned in the previous post “ Humanities Update” we moved 11/12 data from the 11/12 descriptor into iPaMS and put it into the 12/13 format to help Humanities work on their 12/13 data. The third descriptor we have is known as “Phase 1 descriptor”; this was used to import 10/11 data from the phase 1 project of iPaMS.

Module Template

We are now working on making a few more descriptors in iPaMS that will allow us to start archiving College data. The first descriptor we need is a “DWAI descriptor”. DWAI is the system used by both Humanities and SSIS (Social Science and International Studies). One problem with this system is the data does not follow the standard descriptor format made by faculty office that the other Colleges follow. In fact, DWAI holds only one template that has been used throughout the years, as far back as 03/04. This means we will need a whole template dedicated to DWAI which will allow all data to be imported onto this one template from both SSIS and Humanities.

We have also worked out we need three more templates to be held in iPaMS, one each for 06/07, the revised 06-08 and the 08-12. The changes between the templates are only slight, such as merging/ splitting of fields, but to be able to archive the data correctly these templates need to be made separate.

The next step, once all the templates are made in iPaMS, is to bring the archived data in from Humanities and SSIS and then start work on copying and pasting CLES’ (College of Life and Environmental Science) data in by hand, as their modules are all held on word/pdf. We will then look into importing data from the Business School and EMPS (Engineering, Mathematics and Physical Science) as they each have separate databases.