Is the user who defines her/his own CV?
Users cannot change all the contents of their CV; they can only fill out the fields that are available for them. These fields, once filled out, will need to be verified by the competence coordinator, so you should have an SOP or a policy to define how you level each competence.
An interesting idea is to number each level with some very intuitive text because the easier we make it for people to fill it out, the more straightforward it is and the better the chances that they will fill it out correctly. But of course, it's very nice to have some sort of guide or work instruction that supports how they're supposed to pull it out.
If they were to download their CV, they're only going to be able to download it in the template that you have configured. So, if you have used a document type, or you've pre-configured it in the module’s settings, that is the only template that they will be able to use when downloading the document. Unless, of course, they're an administrator or a manager. Then, they can create additional templates within the system, allowing everyone, not only themselves, to choose different templates for downloading their CV.
We already have our competencies and CVs set up in an Excel spreadsheet. Is there any way that these can be imported into Scilife so that we do not have to set this up manually?
Certainly. In these cases, you can reach out to us, and we can align and set up an import meeting. We would be more than happy to help with the import of all the competencies and CVs, and you would be up and running very quickly. Of course, the hard part is the design, setting up, choosing which information is relevant for you, and how to categorize it… But if you already have all of that, and it's already defined in an Excel spreadsheet, we can really help you import the data.
