You are here: Home old structure Teams IT Team Specifications CV

CV

  • persons can create cv
  • cv should be standardized
    • arbitrary choosable number of date-selection text-field combinations for what you did and when
    • list of standard skills/knowledge with 4 levels (no-clue, beginner, intermediate, expert). (skills/knowledge = C, C++, php, zope, ...)
    • certificates related to these skills
    • seperate the same again for language. Each language divided into reading, writing and conversation
    • certificates related to languages
    • any other certificates
    • field(s) of studies
    • field(s) of interest
    • some text areas for other comments
    • fulltext search and specific in field search needs to be possible
  • cv is generally private
  • person can publish cv
  • published CVs get a chiffre code assigned and are then anonymously searchable
  • anonymous means no connection between persons and CVs - not that the searcher is anonymous
  • people who want search access should apply for an account for that, so we can track who is searching our database
  • company looks through them and gets interested in one
  • company requests contact information
  • cv's owner is asked for permission
    • permission granted -> money to eestec -> contact to company
    • permission not granted -> mail to company: sorry person is not interested
Document Actions

seach by different country

Posted by Ceh at Sep 13, 2005 06:17 PM

If a company or a user is interested in students from a particular country

personal data

Posted by tijana at Sep 27, 2005 02:44 AM

maybe it could be good to add fields like age, sex, major subject etc.

In what you did and when, we should define when and which University person graduated from; internship experiences; organized/participated professional events; working experience.

personal data

Posted by Florian Friesdorf at Oct 01, 2005 03:28 PM
I would help discrimination by sex or age. A company should be interested in qualification and that they can search. When they see that somebody meets there qualification criteria adn then decide they do not take him because he is male and too old, it is their decision - however they should see that there is somebody qualified for the job.

About searching for major subjects, internship experience and the like - I think it would be enough if a full-text search over all fields is done. Means: A search for optoelectronics would reveal everybody who did either some majors in opto or and internship or whatever. If we see that there are too many results, we could think of further limiting the search.

Still doing a full-text based search but giving different importance to different fields may be a good approach. You still get everybody how was concerned with opto, but you will get those, who did an internship about it, first.

'It would help' not 'I would help'

Posted by Florian Friesdorf at Oct 02, 2005 10:32 PM
typo correction

Re:personal data

Posted by Ceh at Oct 04, 2005 05:15 PM

This is true, that this could help the discrimintaion, but I think that they can find out this by the names more or less, so it is not so relevant thing. However it would be good for our onw EESTEC analyzes. I think we should also look at this aspect.

search by country

Posted by Florian Friesdorf at Oct 01, 2005 03:31 PM
It might be convenient for a company to search only in a special country. However I think we should emphasize that we are one "country" and that they can search for a EESTEC person who is qualified for the job. It is up to them to say "hmm - well she is qualified, but people from HinterOberAmmergau we do not want" But they should see that there is somebody living in HinterOberAmmergau who would be qualified.

Search by country No.2

Posted by Ceh at Oct 04, 2005 04:48 PM

Well but they could alsop be interested in the people from a particular country,..but it is true that they could also get that data, just by searscingh the qualification and looking where are the students from. Maybe we could have country search on the second lower level. by this I mean after searching for qualification, then you can search for country as well (and other thing we will determine).

Active EESTEC-ers

Posted by Ceh at Sep 13, 2005 06:23 PM

May be people who are working activly in EESTEC (one of the LC's) should be somehow colored differently, or exposed when searching trough CV's. We could also add an option, that a searcher clicks some let's say "EESTEC" icon and this displays what "EESTEC skills" does this person have (e.g. organizing events, working in team, dealing with tehical part of the workshops, logistics, negotiating with companies, managment skills,...)

active eestec-ers

Posted by Florian Friesdorf at Oct 04, 2005 06:05 PM
I dont think we should prefer active people over alumni. Everybody in our database was active at some point, otherwise he/she would not have an account on eestec.org and would therefore not be in the cv database. If somebody messed up with eestec and was thrown out and is therefore not active anymore, then he/she also does not have account anymore.

I think the EESTEC skills are a nice idea, however, I dont know how we should ensure the correctness of the data. We should not just gather all possible "information".

Active EESTEC-ers

Posted by whatever at Apr 02, 2007 10:09 AM
People should think for themselves to put their work for eestec on their CV. This should fit with your other experiences from the past.

reading Borut's doc...

Posted by tijana at Oct 03, 2005 03:08 AM

...I came across some points I would add here: - Total years of your studies - Current year of studies (option: already have a bachelor/diploma) - I am interested in:

also

Posted by tijana at Oct 03, 2005 03:11 AM

what you did and when, field search etc. have to be defined. I'd take it from doc. Borut sent.

what you did and when

Posted by Florian Friesdorf at Oct 04, 2005 04:03 AM
What you did an when looks like this:

timespan - text

Nothing more nothing less. This should be enough to get a structured enough CV.

field search

Posted by Florian Friesdorf at Oct 04, 2005 04:05 AM
Further specification of field search is left out by intention. It must be possible (from the way it is programmed) to implement a field search at a later stage. I think, however, that a google style search is enough and even better than field search.

replay: filed search

Posted by Ceh at Oct 04, 2005 04:53 PM

Well this is not a bad idea to search trough CV's. But doesn't it raise a question what if somebody types in SEARCH BY: " name of the country" and again gets out only the specified countries out. Did you mean to search trough like in GOOGLE, that every word can be searchable, or how exactly do you see it.

field search

Posted by whatever at Apr 02, 2007 10:12 AM
But how would you treat private CV's?

year of study and total years of study

Posted by Florian Friesdorf at Oct 04, 2005 04:07 AM
this information can be clearly seen in the what you did and when fields.

RE:year of study and total years of study

Posted by Ceh at Oct 04, 2005 04:58 PM

Well I think that everything shouldn't be only written in the text fields. Because the information people are entering can be very useful for us. To see how many 1st,2nd,3rd,....year students do we have, what are their interests, possible past jobs, what do they study, are interested in, what are their special skills, for different indicators what are our members and nom members doing,...(we don't have to display it all to the firms). I think (correct me if I am wrong) that it is easier to analyze data if it is written each data to a special table and row. If I am not right, correct me, because I am not so familiar with database constructions.

Why put CV on EESTEC.net?

Posted by whatever at Apr 02, 2007 10:17 AM
To be honest I have to ask why a user should be putting it's CV on EESTEC.net? I mean, EESTEC barely has interesting contacts with companies while EESTEC gets the money for my CV? I don't see any advantage in that.

Partners and sponsors: