CV Builder – Final Report 1.

0 (Draft)

8th September 2008

JISC DEVELOPMENT PROGRAMMES Project Document Cover Sheet PROJECT REPORT Project
Project Acronym Project Title Start Date Lead Institution Project Director Project Manager & contact details CVBuilder October 2006 Nottingham Trent University Ian Griffiths Francis Lowry Information Systems Nottingham Trent University Nottingham NG1 4BU Tel: 0115 848 8514 Email: francis.lowry@ntu.ac.uk Partner Institutions Project Web URL Programme Name (and number) Programme Manager New College Nottingham West Nottinghamshire College www.ntu.ac.uk/cvbuilder e-Learning capital programme (0306) David Kernohan Project ID End Date October 2007 Hosted Shibboleth Base CV Builder for the East Midlands area

Document
Document Title Reporting Period Author(s) & project role Date URL Access √ Project and JISC internal √ General dissemination Final report October 06 – October 07 Francis Lowry – Programme Manager 13th October 2008 Filename CVBuilder – Final Report

Document History
Version 0a-0d 1 2 September 08 October 08 Date Internal drafts Draft submitted to Programme Director, Project Team Final report submitted to Programme Director, project team and partners. Comments

Page 1 of 21 Document title: JISC Final Report

CV Builder – Final Report 1.0 (Draft)

8th September 2008

Hosted Shibboleth Base CV Builder for the East Midlands area (CVBuilder)

Page 2 of 21

CV Builder – Final Report 1.0 (Draft) 8th September 2008 This page is left intentionally blank Page 3 of 21 .

................................... 9 Implementation................ 18 Conclusions...................... 20 Appendixes............................................................... 5 Executive Summary............................................. 21 Page 4 of 21 ................................................................................................................................................ 5 Background........................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................................ 7 Aims and Objectives. 16 Outcomes............................................................. 20 Implications.............................................................................................................................................. 14 Outputs and Results............................................................................................................................................................................................................................................................................................................................................................................................0 (Draft) 8th September 2008 Table of Contents Acknowledgements.......................... 8 Methodology.................................................................................................................CV Builder – Final Report 1.......... 20 References..............

For various reasons detailed in this report. New College Nottingham and West Nottinghamshire College. and the UK Federation was primarily concentrated on the technology. We would especially like to thank the East Midlands RSC for providing us with valuable input with respect to proofing our Shibboleth installation processes. and giving us a platform to communicate more widely to institutions in the East Midlands. Collaboration with partners. The Shibboleth mail lists. A positive point is that all the specific data elements identified within the CV analysis had a corresponding element in the specification. Support for Shibboleth. With the exception of placing the Web Services framework into a production stage. Page 5 of 21 . the release of the software as open source appears to reduce the potential market for subscribing to our service. Rather than just provide our previous installer and supporting documentation. NTU Executive Summary Development of a CV Builder tool The primary aim of the project was to create a CV Builder and publish it as a service for use by educational institutions in the East Midlands. We were keen to find a good example demonstrating the types of services and systems that could be developed. CVBuilder as an exemplar for UK Federation and shared services. and the primary Shibboleth Wiki have also proved an invaluable resource while working through some of the more detailed technical aspects of Shibboleth. although though not a complete surprise. the development has been completed and we are in the process of launching both the service and the tool as an open source product. Although delayed within the project’s original timeframe. the actual development and idea has enabled us to get conversations started about the benefits of federated access. as the set of data elements actually used within a CV is considerably less than that supported by UK Leap. especially in the period since JISC and Eduserv announced the ending of JISC funding for Athens services. The project would particularly like to acknowledge the help and support of the following: • Clive Church JISC-CETIS and Edexcel. Federated Access. West Nottinghamshire College • Paul Hacking.CV Builder – Final Report 1. we completely overhauled our previous work in this area and produced a full end to end set of documentation for implementing Shibboleth on Windows. promoted and facilitated by having a federated access framework in place. Although. Mapping the data to the UK Leap specification was not as fruitful as anticipated. • Shirley Blakemore New College Nottingham • Liz Butterworth. and it’s replacement as the authentication framework for Athens. we have successfully completed and implemented all the functional components of the system. The research and modelling of the new system was based on analysis of CV’s currently in use and best practice as promoted on on-line recruitment companies. Project partners were: Nottingham Trent University. the emphasis on the Shibboleth aspects of the project shifted from a secondary aim to having equal weight in terms of effort and import to our partners and the FE community and universities with a comparable technology stack to us. Our perception of the environment at the onset of the project was that the emphasis on Shibboleth.0 (Draft) 8th September 2008 Acknowledgements This project was conducted under the JISC e-Learning capital programme (3/06). This work has been very well received. originally from West Nottinghamshire College • Keith Mellor.

As well as the shift in emphasis on Shibboleth. we have been able to work more closely together in particular on Athens migration issues and changes required to support this.CV Builder – Final Report 1. outside of the formal project.0 (Draft) 8th September 2008 A very positive outcome has been the increased work and support within the project partnership. Page 6 of 21 .

CV Builder – Final Report 1. implementing the enhancements previously identified.0 (Draft) 8th September 2008 Background This project has built upon the work undertaken by Nottingham Trent University as a sub-project within the “Regional Interoperability Project on Progression for Lifelong Learning” (RIPPLL) project funded by JISC and undertaken jointly with the University of Nottingham. SQL Server etc.e. were well known and we had clear ideas of exactly what was needed to be done to improve it. the benefits that could be realised once they stopped focusing on Shibboleth as a replacement for Athens. The combination of taking our existing CV Builder. IIS. its purpose. We wanted to take the opportunity to develop a production system demonstrating they type of services that could be developed across organisations once a working shibboleth infrastructure was in place i. The underlying technical component of the EMSS project was Shibboleth and it’s implementation in the Microsoft Windows environment. In order to ensure that we had a live environment to run the CV Builder system through. the CV Builder itself only allowed you to order data sections and include / exclude specific sections. it was imperative that all three organisations in the partnership had functioning shibboleth infrastructures. Of the two existing products. In addition. it only allowed for one CV. Limited presentation options i.doc and open in Word. the CV Builder was chosen as a tool for further development primarily because it’s limitations i. output was as HTML and you could only download it as a . if you wished to produce multiple CV’s for differing purposes. Both of our partners had complementary technology infrastructures. we had identified that both our existing PDP and CV Builder solutions were very inflexible in what they could do compared to what was technically possible now and that they both did not facilitate easy transitioning of learner data. shifting the focus from Shibboleth the technology to the opportunities afforded by a federated access framework.e. and it’s relevance to learners of all ages is universally understood. and then save the output as a Word document. given that the term Curriculum Vitae (CV). so our existing installation processes developed through the EMSS project could be enhanced to encompass their environments and the combined output could help assist other organisations with a similar infrastructure. The work within the RIPPLL project focussed on the transition of a subset of PDP data via web services using Shibboleth as the authentication framework. and re-engineering it’s login and authentication framework to utilise Shibboleth. • • • Single CV i. Active Directory. you had to edit the data each time.e. Through our previous work on EMSS we identified that a lot of institutions did not realise what opportunities would be made available once they were part of a federated access framework i. gave us a very demonstrable and immediately practical solution.e. Limited formatting facilities i. and previous NTU JISC project work on the East Midlands Shibboleth Service (EMSS). Windows Servers. Through previous work with the RIPPLL project and our focus on the transitioning of PDP data using UK Leap. although you could customise a Word document after the fact.e.e. Page 7 of 21 .

No changes were made to this objective Based on agreement from the partner colleges to support them to the degree that they could be selfsufficient with respect to Shibboleth in conjunction with feedback from other FE colleges in the East midlands. we extended the objectives relating to Shibboleth to cover the whole end to end implementation of a Shibboleth framework on windows.e. 4. Identify local learner data (where the data already exists) that can be referenced by the CV Builder service. Changes: The objective has not changed. Develop and deliver complete installation instructions of a Shibboleth Identity Provider on Windows. 5. these basic PDP components required to build a CV will be made available via web services from each partner institution. Objectives and how they changed during the course of the project 1. This implied a fundamental shift from using our Shibboleth ‘Installer’ from the EMSS project which created a black box solution. The idea being that this could be taken by anyone with no experience or knowledge of Shibboleth or its dependant technologies and implement a fully functioning IdP. componentised installation process. Page 8 of 21 . for self promotion or migration to another PDP system. Develop and deliver installation instructions for a Shibboleth Service Provider on Windows.CV Builder – Final Report 1. No changes were made to this objective 3. Implement Shibboleth IdP at partner institutions where it does not already exist so that members of each partner institution can access the CV Builder. as delays in the completion of the Web Services framework meant that it was not possible to identify to a granular level which data would be provisioned for the partner colleges. No changes were made to this objective 6. Where possible. from each institution. over and above ‘just replacing Athens’. No changes were made to this objective 2.0 (Draft) 8th September 2008 Aims and Objectives The primary aim of the project is to develop. 7. Changes: Due to delays in the project and resourcing conflicts it has not been possible to undertake and complete this work at this time. Explore the mechanisms to digitally sign local qualifications and evidence of learning etc. however the framework is at the internal testing phase at this point and has not progressed sufficiently to allow partner colleges to do testing. build and deploy a service which will enable any learner with a Shibboleth account in the East Midlands area to create dynamic CV. No changes were made to this objective 8. The hope is that this will demonstrate how the UK Federation and the Shibboleth infrastructure can enable institutions. Changes: This has only been completed for Nottingham Trent. to a fully documented. with detailed instructions for each phase. incremental. Develop a CV Builder data repository where the learner can store all the components required to build a CV in a relational database with appropriate web based data entry and management screens. Develop a mechanism to allow a learner to access or publish their own CV data outside of the Shibboleth protection i. The secondary aim of the project was to provide support for the installation and configuration of a suitable Shibboleth environment with both our partner colleges with the provision of appropriate learning materials and documentation to allow other institutions with little or no knowledge of the technologies supporting Shibboleth to implement their own environments. Develop a framework to allow remote learner data to be referenced by the CV Builder service using Web Services protected by a Shibboleth SP at each partner institution.

Through the project we have identified additional functionality. With the Shibboleth environment in place between us and our partners we would have a broader test bed for functional evaluation and refinement of the finished product. We plan to continue work on the CV Builder functionality and complete and extend the components for the web services past the formal end of the project.0 (Draft) 8th September 2008 Figure 1 . each with their own approach.CV Builder – Final Report 1. Specifically take out version of a Shibboleth implementation on Windows and work in through with institutions with a comparable IT infrastructure. then ‘bolt-on’ the changes required to support life long access and integration with the shibboleth framework. For CV Builder. Methodology Overall Approach Within the project there were two core streams of activity CV Builder and Shibboleth. For Shibboleth. detailing how to install and configure all components. already having a product in place with all the basic functionality. features and facilities that we now plan to implement for a version 2. the original idea was to extend the system by adding functionality already identified based on existing user feedback. Page 9 of 21 . the planned outputs were to document our knowledge and experience of implementing Shibboleth on the windows platform and share this.NTU Shibboleth IdP components From our experience with the information available in the Shibboleth community at large. however it was very distributed and there was still nothing that gave a full and detailed end to end installation instructions to implement an IdP from the Windows Operating system upwards. there was a wealth of information on how to implement Shibboleth.

though not unexpected. we sourced as many different CV’s. 6. We had the technical staff available with the skill sets necessary to proceed on both fronts in parallel. Overview of analysis process: 1. this meant that our intentions to map and perhaps provide some additional information to feed back to the UK Leap specification would not lead to much. and we would be able to take this a stage further and use this to support our partners with their shibboleth implementations. Get all section headers from all CV’s – note the Header is a section header in it’s own right. 2. however the detail of the ‘where’ was extremely sparse and usually consisted of just an institution name! To facilitate transitioning the data onwards. Except to say that for each of the sections and data fields there was a direct map. Page 10 of 21 .0 (Draft) 8th September 2008 Rationale for approach For CV Builder. Most of the data sections included some reference to where a particular activity took place. detail the data elements and types required to store the data in a relational format. Unfortunately. the Web Services and Digitally assigning CV assertions etc. First of all. using templates publicly available from private and public sector organisations. Research In order to determine what currently constituted a CV and to ensure that some we had not excluded some key details. and where possible real CV’s from colleagues and analysed the contents. 3. we added Institutions as a new data section. Leuven. With respect to Shibboleth. public examples from on-line recruitment agencies. and defined a minimal set of data (primarily the institutions address) for it.e. we then abstracted the fields within them and worked out which pieces of data were the most common. Create a matrix within a spreadsheet and count the occurrences of the different section headers – not making any assumptions at this stage Create a new matrix. A good example of this is with Institutions.U. identify the core sections from the original matrix and map the original sections to the core For each section. the extensions and amendments could be implemented reasonably quickly allowing what we considered to be the added value components of the project to commence quickly i. 4. 5. that the numbers of elements of data required were substantially less than what would be expected of a full PDP system. Map each data element to the corresponding section in ukleap Create initial data model It was very noticeable. given the existence of the current product. structure and layout. however the UK Leap specification is considerably more comprehensive. we already had the installer – customised from the work done at K.CV Builder – Final Report 1. the sections within the CV were aggregated and we came up with a master list of discrete data sections that was common to all: • • • • • • • • • Personal Information Address Details Telephone Numbers Email Addresses Websites Training and Education Qualifications Achievements Employment • • • • • • • • • Career Aims Interests Personal Skills Competencies Research Details Publication Details Institutions Additional Info Referees For each data section.

Data . Dual authentication entry points – Shibboleth and non-shibboleth. It is this alternative login account which allows an individual to either join shibboleth accounts as they move from institution to institution.reuse many times. 4. this did lead to the decision to allow a free text field for each data record. support better mapping to standards e. 3.break data elements into reusable chunks i. Data . UK Leap. In a lot of cases this was used to contextualise the information e. CV Builder Functional Design The core principles of the design for the new CV Builder: 1. Page 11 of 21 . Separation of user’s identity record from their Login. 8. there was always a handful of CV’s which had a free text element within that section.g.CV Builder – Final Report 1.e. Output of editable hard copy. 2. 9. 6. Support for Shibboleth Authorisation – through the use of eduPersonEntitlement. 10. for an Email Address. a user is forced to populate some basic data fields and create what we have described as an Alternative Login account. 7. Multiple different presentations with the same data. Online (Web Based) publications in addition to hard copy. Although contradictory to our philosophy of maintaining the data at the most granular level possible.0 (Draft) 8th September 2008 One final observation of the data was that irrespective of the data section concerned. The separation of the user’s identity record within CV Builder from the Login id was the core decision to allow us to provide facilities for Life long learning. 5. Specific data selection for specific CV presentations. there would be a note to say this was the best way of contacting the person etc. or enable them access to their data after they have left the educational environment and no-longer have access to Shibboleth.Enter once .g. On initial login via Shibboleth. Functionality must be intuitive to the end user.

and to reduce vulnerabilities. based on our outputs from the RIPPLL project. Complementing our Shibboleth infrastructure. the development environment for CV Builder was all based on Microsoft Technologies.CV Builder – Final Report 1. support transitioning of the user data and future interoperability. or stored procedures. and that all data and output generation would be sourced from the database.0 (Draft) 8th September 2008 Figure 2 . one fundamental design decision was that all data entry elements would be recorded in a relational database.CV Builder Use Case diagram CV Builder Technical Design In order to ensure the best fit to UK Leap. To support this. we needed to ensure that all data stored was recorded to sufficient granular detail to allow us to describe it effectively using XML. Page 12 of 21 . To ensure optimum performance. all data manipulations were performed through either a class object referring to a database table.

Once a student completed. JA-SIG’s CAS provided the Single Sign-on (SSO) component. A key change to our Shibboleth implementation approach was the entry to the UK Federation and the adoption of it rules of membership. Page 13 of 21 . we decided the Active Directory would only provide the Authentication request. We facilitated this by creating a CV Data Selection entity. Core NTU Decisions: 1. In order to provide us with the flexibility to be able to have multiple different presentations of a CV.0 (Draft) 8th September 2008 • • • • • Windows 2003 Server SQL Server (2000 & 2003) C# . we recognised there was no ‘correct’ way of implementing Shibboleth and that key aspects of the implementation were at the discretion of each institution. From earlier experience. we designed a simple framework. which allowed us to specify XST chunks which could be added together to deliver the formatted output we needed. we would remove all attributes from the database. hence complying with federation rules and continuing our service to our students.1 of the UK Federation Rules of Membership: “6.1. when it became apparent that CSS on it’s own would not provide the flexibility we wanted for the Layout Manager and that we would need to use XML Transformations (XSLT). or at least no Attributes must be asserted for such End Users to the Federation. Every other decision was based on the recommended Shibboleth IdP implementation. and that we would source the attributes from a SQL Server database. all driven from the database. however. Active Directory for Authentication only 2.4.” Our original Shibboleth installation sourced attributes from Active Directory. and what was an NTU decision. we needed to separate Data Entry from Data Selection. credentials of End Users who are no longer members of the organisation must be revoked promptly. Shibboleth The strategy adopted in creating appropriate instructions for implementing Shibboleth was to take a clean machine and work through all the steps required to install it. specifically the rule 6. This included documenting as many ‘problem’ areas as possible. we opted to clearly articulate what was a Shibboleth IdP requirement. however rather than provide instructions for every option. Rather than attempt to change university practice. we have a practice at NTU that graduates are able to access network resources for example home directories etc. Shibboleth attributes sourced from MS SQL Server 3.CV Builder – Final Report 1.NET ASP – primarily for prototyping Internet Information Server (IIS) At later stages. for 8 weeks post their official leaving – this gives them more time to tidy up things. and managed Layout and Styling as additional discrete processes.4.

CV Builder – Final Report 1. Shibboleth Support and Documentation The split of roles within the project meant that in order for out partner colleges to support the development and testing of both the infrastructure and CV Builder. we worked with our partners and the East Midlands RSC. the sequencing and parallel running of activities was designed around the resources available at the initiation of the project. it was no-longer possible to do so. Resourcing At the outset of the project. Provide input into data requirements for CV Data. The documentation referred to in this section is available on our project Wiki space. This documentation was designed as a standalone set of instructions. The split of responsibilities between NTU and our partners left NTU responsible for the core development both with CV Builder and the implementation of the Shibboleth infrastructure. The loss of staff at NTU also meant that where we had been able to run the two streams as parallel activities. The lead at West Nottinghamshire College changed this caused a slight delay in getting the whole group together.0 (Draft) 8th September 2008 Implementation The original work packages for the project were developed by the development team in a workshop. crash & burn and training environments. Using an Installer to do the work of installing and configuring Shibboleth is a very efficient way of getting going quickly. they fell into the same trap as other existing materials and closer to the end of the documentation started to assume knowledge and information that had not been provided. • • • Proof the Shibboleth installation process and provide testing of the Shibboleth framework for the web services. In addition to this our ability to support our partners using the installation script was seriously compromised and we needed to close this knowledge gap. at the first meeting we discussed and agreed changing the Shibboleth work to extend it to include full end to end documentation to enable our partners to be self-sufficient. CV Builder tool itself and the Shibboleth infrastructure to support it. Test CV Builder and Shibboleth access. and we had to start to sequence the activities more based on our resource constraints. Within the project. Although we had lost several months working on the installer. we needed to reprioritise the activities around Shibboleth and extend our original remit around Shibboleth. however it did not provide the user with an in depth knowledge of Shibboleth and it’s pre-requisite technologies. hosting a training session at NTU where we proofed the materials prior to publication. and our partners with several roles. Page 14 of 21 . we were confident that we could deliver and we decided the best way to do this was to design an implementation process which worked through each component in detail and document each step in turn. With this context. An interesting observation from the training is that given the detail level the creators of the training materials were working at. there were a few losses which had an impact on the start of the project. After internal testing and proofing. With the loss of our key development resource. the limitations with our previous shibboleth installation approach became more apparent. We sourced a suitable server and used multiple Windows 2003 VMWare images in a development / test. NTU lost the key member of staff who had all the detail knowledge of Shibboleth and the work on the previous JISC bid. there were in effect two completely different tracks.

implied that the existing data model for the current system could not be extended. one of the prime impacts was as we had designed the project and distributed the workload across a longer period it was easy for IS project managers outside the project to open their resource negotiation with statements like ‘Your project runs for another year. when we finally got to the layout manager phase and designing. NTU embarked on a project to replace its existing in-house developed Virtual Learning Portal (VLP) with a commercial Virtual Learning Environment (VLE) purchased from Desire2Learn (D2L). In addition to this. the same resources that managed and maintained the incumbent VLP. With hindsight. having to go back to basics and redesign from scratch meant that we missed the window of opportunity to make the new CV Builder available ready for the NTU internal users. Unfortunately as the layout manager components were the last component to be developed. there has been a noticeable impact on the delivery and organisation of the project. NTU Information Systems adopted a policy of formal resource management for all projects involving IS. The resources required to support the evaluation and implementation of the new VLE were. We hope to get back to this part and put a more robust rtf / doc generator in place. it failed it’s usability tests and we found that although we could get CSS to happily layout the page and style it. This led to some very interesting discussions regarding resource prioritisation.CV Builder – Final Report 1.doc rather than a native . Our original intent for the output format was to use CSS. Although each change has led to an incremental improvement in both organisational and environmental conditions. The main rationale for this is that despite the flexibility offered by the layout manager. With the reorganisational changes. this proved to be a blessing in disguise. surely you can catch up a couple of days over the next year or so’. we identified that the separation of the login name from the user’s internal identity and the enhancements to make the data model more granular. Unfortunately.DOC or . Information Systems have been implementing a step change in how we work.0 (Draft) 8th September 2008 CV Builder Development When we managed to start work on the CV Builder tool itself four months into the project. With this in mind we decided to create a new product from scratch. I only need the resource for a few days.CV Builder process flow The requirement for static fixed format output i. Organisational issues Through the life of the project. unfortunately. users still wanted to ‘tweak’ the layout of a hard copy version. we short-cut the development process and provided quick solution to download a html file as a . The CV Builder works on the sequence: Figure 3 .e. Rather than design the whole data model first then build the forms. the PDF output reduced considerably as users started to work with the tool. Page 15 of 21 . it was not possible to use CSS on it’s own to allow on-line interactive template management.rtf file. and shifted our database design and development approach to a more agile model. during this same period. we designed each functional area based on the CV Builder use case diagram (See Figure 2). to control the layout and design of the CV.

through the project. and communications to the wider programme group.e. raised the emphasis on Shibboleth and we were asked to provide more details and present the Shibboleth aspects of the project. as we do not store any physical artifacts i. giving them longer chunks of consecutive time over wider gaps. This is currently available in our project Wiki. The key area to suffer was around the formal project communications.0 (Draft) 8th September 2008 Given this and given the new internal structures in IS. we created and published full documentation on an end to end implementation on the Windows platform. this was not identified as an issue until late in the project where very little could be done to fully recover the situation. but reference them via a web link. source code and installation instructions will be published within the project Wiki. all the development notes. Word Documents. interest in the hosted service is considerably less than interest in getting the source code! We are finalising the service cost. this tool will be offered as an on-line service to institutions who are members of the UK Federation in the East Midlands once our partners have signed off on its suitability. This includes the data model and design. Lesser outputs include some of the design and technical components of the CV Builder itself. This will be released to the wider community as an open source product at a launch being organised for October 2008. However we will be continuing our work in this area and sharing our findings. it was necessary to restructure how resources were allocated to the project i. the storage requirement per user is very low – we have not agreed as yet whether to make the cost for an institution accessing the service a nominal low fee. or wave the costs altogether. We have no issues with anyone else picking up this code and continuing the development in a more collaborative way. media files etc. Unfortunately this plan restructuring did not happen immediately and the conflict between the original organisation of the project and the new way of managing resources lead to interruption in the time allocated to the CV Builder aspect of the project and consequent delay in the development of the CV Builder. we also used Linux VMWare images to prototype various Shibboleth configurations and deployments. XSLT and CSS generators etc. Outputs and Results The substantive outputs from the project include the new CV Builder tool for use within NTU. In addition to the planned Shibboleth on Windows work. Project Management The original project plan included the project manager with a design and development role. why would I go through the extra formal hoops to sign up to an external service when I can. is that informal feedback from presentations to FE Colleges at the various RSC events attended was ‘if the full functionality is going to be available as open source. at the moment. the outcomes and instructions for this work has also been published in the Wiki. At this point. We have recognised this internally within IS and have made appropriate structural changes to ensure that this will not affect other projects. more easily implement and host it for our own students’. Images. Page 16 of 21 . Primary dissemination activities concentrated on local FE colleges through the East Midlands and Eastern RSC’s. design materials. With respect to Shibboleth. At the launch.e. Feedback from our Careers team confirmed that the additional functionality did meet and close the functionality gaps. We will not be managing the CV Builder as a collaborative open source project as we have internal drivers and needs to be met – specifically exploring closer integration with the D2L e-Portfolio tool. One minor snag with respect to the service.CV Builder – Final Report 1. In addition. this proved to be a poor decision. with the other organisational changes underway. the database driven XML. The outcome from the JISC – Eduserv discussion around on-going Athens provision.

it did not enable us to provide more useful feedback. Page 17 of 21 .0 (Draft) 8th September 2008 The outcome of the CV analysis was slightly disappointing with respect to UK Leap. The CV Data appeared to be more a subset of UK Leap than originally anticipated. although this to a degree ratifies the UK Leap specification.CV Builder – Final Report 1.

Page 18 of 21 .0 (Draft) 8th September 2008 Outcomes Project achievements against aims and objectives set Aim The primary aim of the project is to develop. however the deployment of the Service has been delayed pending successful final testing and completion of some contractual documentation – it is anticipated that this work will be completed before Christmas 2008. Although loss of staff did impact on the delivery dates for this. and we complete the help documentation. we are confident that the new version is a superior product. build and deploy a service which will enable any learner with a Shibboleth account in the East Midlands area to create dynamic CV. We already have a list of things we want to add for a version 2 and will be continuing with this work past the end of the project. Completed. there is a risk that the service will not be utilised as institutions will be able to create their own copy. This was one aspect of the project where we did not anticipate any issues.CV Builder – Final Report 1. The framework has been developed. We have had excellent positive feedback from users who have taken our instructions and implemented their own environments. over and above ‘just replacing Athens’. The secondary aim of the project was to provide support for the installation and configuration of a suitable Shibboleth environment with both our partner colleges with the provision of appropriate learning materials and documentation to allow other institutions with little or no knowledge of the technologies supporting Shibboleth to implement their own environments. Apart from that. Evaluation Completed – although the first version failed usability tests. Satisfaction of objectives Objective Develop a CV Builder data repository where the learner can store all the components required to build a CV in a relational database with appropriate web based data entry and management screens. we believe we have provided a more comprehensive set of instructions and information which is of more use to the wider community than the original documentation would have been. however we have not managed to proceed past this and actually implement it in a production system. Implement Shibboleth IdP at partner institutions where it does not already exist so that members of each partner institution can access the CV Builder. We have been very pleased with the work eventually delivered here. Develop a framework to allow remote learner data to be referenced by the CV Builder service using Web Services protected by a Shibboleth SP at each partner institution. we will be ‘releasing’ a version 1 to the wider community. given that the CV Builder will be released as open source. all the other work supporting this is complete and we believe we have created a good product and good demonstrator as a Shibboleth enabled service. we are very pleased with the outcomes here. This is one of the internal NTU priorities and we intend to progress this work with our partners past the end of the project and publish our work. One concern. The hope is that this will demonstrate how the UK Federation and the Shibboleth infrastructure can enable institutions. Evaluation The overall aim has not changed. Once signed off internally. Given the change in emphasis at the start of the project in the Shibboleth sections.

personal details and some qualifications. using the Wiki format has enabled us to update and maintain this documentation as and when changes occur. Institutions in the East Midlands will directly benefit from either the central service or the release of the CV Builder tool as open source. these basic PDP components required to build a CV will be made available via web services from each partner institution. Explore the mechanisms to digitally sign local qualifications and evidence of learning etc. Partner colleges will get similar benefits once we release the service as a production service and they begin accessing. juggling resources and negotiating resource availability can be frustrating. enabling better collaboration and sharing of knowledge and experiences. Although available. and consequently deadlines missed and unnecessary rushing around to play catch up ensued. and we intend on exploring how we can integrate either the D2L Tool with CV Builder or Vice Versa. we currently have the situation at Nottingham Trent where we have implemented a new VLE from Desire2Learn. Due to a simple error early on in the project. One key area that will be of immediate use is in enabling the population of the Personal Details sections. • Only undertake a research or new development project with dedicated resource. This is completed. Develop and deliver installation instructions for a Shibboleth Service Provider on Windows. Where possible. This is a disappointment internally. programme communications and information were not being received. • Maintain communications with the larger JISC programme. With the changes in internal IS processing. up-to-date project plan and work packages. My personal preference would be to work on shorter duration projects. Unfortunately. This VLE comes with it’s own ePortfolio tool. was very supportive with this.e. primarily identity. David Kernohan. we feel there is more that can be added here. Page 19 of 21 . The data sets that are available are quite minimal. This has been completed. Life Long learners will be able to easily take their data away. Who benefits? • • • • • • Students and Staff at NTU get the immediate benefit of an improved CV Builder service. In addition to this. Lessons Learned • A two year development project is too long unless you have full time dedicated resources. they can retain access to it for the life of their account. With a current. Institutions who are attempting to implement a Shibboleth infrastructure on windows will be able to work through the online materials.0 (Draft) 8th September 2008 Identify local learner data (where the data already exists) that can be referenced by the CV Builder service. (The JISC programme manager. or if they want. NTU has strengthened its working relationship with partners and the local RSC’s. given the delays with the project this is one of the areas where we have not been able to apply sufficient effort to. NTU will be exploring how we can better integrate with our new VLE. from each institution. for self promotion or migration to another PDP system. and not having full-time dedicated project resources. Develop and deliver complete installation instructions of a Shibboleth Identity Provider on Windows. and we are optimistic that we will be able to continue exploring in this are and feed back our findings to the community. Completed. specifically bringing in formal resource planning across the department. Develop a mechanism to allow a learner to access or publish their own CV data outside of the Shibboleth protection i. Completed very satisfactorily. you can better argue the case for resource commitment.CV Builder – Final Report 1.) • Continually revisit the project plan and update work packages. Once we get the web services framework moved to a production environment we expect to be able to further refine this section. As a result there was a communications failure with the programme manager.

given the simple data entry and data selection screens. and not Shibboleth 2. we were able to work very closely together to identify the best solution. • The CV Builder. providing a mechanism to directly link Skills to Employment. would provide a good building block for an e-Portfolio system. As part of the feedback for CV Builder.uk/media/documents/themes/accessmanagement/eastmidlandsfr. we feel we have now a solid product.edu/display/SHIB/WebHome) UK Access Management Federation (http://www.org/products/cas/) Homepage for the RIPPLL project (http://www. once you have a working Shibboleth infrastructure.ac. • We have a stronger working relationship with local FE Colleges. We do not intend to proceed along this vein ourselves as strategically we will be concentrating on integrating the CV Builder with the e-Portfolio tool within our new VLE.org. we have received comments that as all the data is stored in a database. Page 20 of 21 . • Although we will not be managing the CV Builder as an operational open-source project.uk/) UK lifelong learner information profile Specification BS Draft standard 8788-3:2006 For clarity. however the relational database and application design could theoretically be extended to facilitate the creation of a simple e-Portfolio system.nottingham. effectively implementing a split between development and production support. in particular with both our partners. Developing an application and using Shibboleth as both the Authentication and Authorisation component as very straight forward.internet2. the new way of allocating resources in discrete chunks. References EMSS JA-SIG CAS RIPPLL Shibboleth UK Federation UKLeap Final report (http://www. or Employment to Qualifications etc. institutions will begin to explore the many benefits and possibilities of a federated access framework.jisc.ukfederation. Conclusions We found the project to be extremely beneficial in many respects: • We closed what we perceived as a gap in the community with respect to Shibboleth implementations on Windows. and potentially a example development framework for others to be able to start to develop and deliver shared services via Shibboleth and the UK Federation.uk/rippll/) Shibboleth @Internet 2 (https://spaces. and combined with loss of key resource we were unable to satisfactorily keep both strands running in parallel. despite being delivered later than planned. When one of our partners identified a problem with our implementation of CAS’s LDAP lookup to Active Directory with sub-domains. we will be continuing the work in this area and will continue publishing our enhancements. proved to better support the resource and development approaches required for this type of activity. We were very careful to keep the scope of the CV Builder to just CV’s. We would expect that over the next 12 months. we found that we had effectively two discrete projects. please note that all references to Shibboleth relate to version 1. is a better product than existed before. keep the primary aims as closely aligned as possible.CV Builder – Final Report 1.0 (Draft) 8th September 2008 • As far as possible. Implications With respect to CV Builder.pdf) Open source enterprise single sign on (http://www.ja-sig. • Although the changes within NTU IS organisation initially had a detrimental impact on the project.ac. as the prioritisation of implementing Shibboleth to replace Athen’s authentication reduces.

0 (Draft) 8th September 2008 Appendixes Acronyms ASP CAS D2L EMSS IIS IdP NCN NTU RIPPLL RSC RTF SP UKLeap VLE VLP WNC XML XSLT Microsoft’s Active Server Pages Enterprise Single Sign-on service provided by JA-SIG Desire2Learn East Midlands Shibboleth Service Microsoft’s Internet Information Server Shibboleth Identity Provider New College Nottingham Nottingham Trent University Regional Interoperability Project on Progression for Lifelong Learning Regional Support Centre Rich text format – output file format Shibboleth Service Provider UK Lifelong learner information profile Virtual Learning Environment Virtual Learning Portal – NTU’s in-house developed learning environment. West Nottinghamshire College Extensible Markup Language Extensible Stylesheet Language Transformations Page 21 of 21 .CV Builder – Final Report 1.

Sign up to vote on this title
UsefulNot useful