It was a warm, late afternoon on May 2016, when we at plone-support received a message, asking for help. Perhaps we weren't like Obi-Wan Kenobi on that, but close enough: A customer needed to have a new course registration system and migration from the old one so soon as August 2016. Whoa, three monts, summer coming on and other projects on the road too. Should we just skip it or take the million credits to get even with Jabba?
Well, here's a spoiler alert: https://www.fdpe.fi/
1. The case of The Finnish Doctoral Programme in Economics
A Joint Doctoral Programme of the Economics Disciplines of 10 Participating Universities in Finland. The Finnish Doctoral Programme in Economics (FDPE) promotes high-quality doctoral education in economics in Finland by organising systematic and diverse doctoral courses and seminars.Here's is a rough translation of the initial email we received in May 2016.
We will need a platform, where we can manage nation wide economics doctoral programmes cooperation. To be more clear: we need a web-based system, that allows students from participating universities to apply for doctoral studies courses from another universities. Ideally the principles of the system would be:
- Each university inserts a batch of courses as part of the cooperation
- The courses became a course pool, that will be communicated to the studens via the system
- The students from each univeristy may register for the coursers on the course pool
- After a course a teacher may communicate the grade of each student to the student's home university via the system
- Once per year the registrations are gathered and counted, how many participants there are from university x to university y
- Based on those calculations it is possible to settle the compensation between universityes.
The point is to build a platform to gather registrations and communicate students grades and registration information. The platform should be as simple and robust as possible.
Our schedule is uncomfortably tight in the sense that the system (or at least te application feature) should be online at latest in August.
Ok, so we got the message. And why they chose to ask us, is because of another Plone-site that shows events and gathers applications there: http://inforte.jyu.fi
We discussed about the case, and thought it was quite a challenge to present so late at spring, (with all the vacations and other projects we had in store for the summer). But we also thought, that we had a quite toolset for this kind of system:
- Plone would take care of the website, permissions, workflows, security and robustness.
- Courses would be dexterity content types - easy to create and to modify if needed
- The registration form could be easily created using Plone Form Gen add on - of which we had lot's of experience
- The information about participants could be delivered in the system using plone permission management and intranet features
- This was a good case to try out new Plone 5 and its out of the box responsive layout
So we were set to talk with the customer and see what else they might have in mind.
After a positive meeting, we also had this information:
- Migration was needed, but only for visible content
- The visual desing of the site would be secondary feature
- If only the application forms and course information were online already in August, the rest of system could be finished by September
- We could use HAKA indentity federation service to allow students and staff from different universities to login with their own userid and password. We could have created internal useris's for the admins and could have forced students to insert more information at the application form, but this was way better solution. We had used HAKA before with Plone in many occasions (Like Moniviestin video publishing platform)
- The couldn't use national Opintopolku.fi -service (at least not yet) for doctoral studies.
- The project had fixed deadline and the customer was willing to prioritize and to focus on the most important features first
2. Plan B.Actually, we had no plan B, so we came up with plan A, to divide the development into clear phases, visible to the customer:
- At first we would set up a preview-site: the customer could then start using Plone and to learn how to use it.
- A light theme customization
- Site name, domain, certificate and HAKA-federation bureaucracy was set to motion
- Migration to the old public content (scrape public content)
- Shibboleth-integration (HAKA) development for Plone 5
- An event like Course content type would be created
- Using a Plone Form Gen -solution we had created before on another case to automatically populate basic user information about the person filling the form.
- Using a previous solution to generate reports on every separate application form.
- A Plone folder, where a teacher stores the saved Excel-files about course grades
- Other features, like managing permissions, communication, instructions, planning the application form and theming.
|So, we had plans.|
The actual work
When the migrated content was checked and deemed okay, and the bureaucracy with the domain name done, we published the new site in june 2016 - only without the form functionalities. However, the customer could already do some content editing and checking that everything was okay.
Last, but not least, we developed the registration form and a new content type called Course, with some basic data (start date, end date, information). When a student goes to a course, there is a registration link which opens the form with all necessary fields already populated. The registration form was done using Plone FormGen add on. We had used that add on for over a thousand forms at JYU, so we knew it was stable and customizable.
The registrations were collected to a .csv-table, easy to open in Excel or Google Sheets and easy to use from every organization participating FDPE programme.
In the end we created short instructions for the site admins on how to manage content. The instructions were just Plone pages with some images and links.
Example one: Course Page
Example 2: Registration Form
SummaryThe customer was very satisfied with the development and results, and so were we.
This kind of development in this short time period wouldn't have been possible if we didn't have the suitable technology available and knowhow on how to properly utilize it.
Additionally the customer was really cooperative - they focused on getting things done, they did their part on the content and other bureaucracy, and most importantly they knew what to prioritize.
We had limited time and limited resources - and usually it is a good thing if you can actually prioritize and altogether just cut out some features if needed. First things first, and then some.
By using free Open Source components and no need to pay any licence fees, the only thing we (and the customer) needed to focus on, was the actual development.
Now, after almost a year of usage there has been near to none feature requests or incidents using the system, and definitely nothing major. But there have been hundreds of successful registrations and everything seems to be working fine.
If you want to know more, please contact email@example.com
It is party time!