Archive for April, 2012

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.