Difference between revisions of "Pubman Func Spec Researcher Portfolio"
Jump to navigation
Jump to search
(→Data structure: added on data structure) |
(update) |
||
| Line 2: | Line 2: | ||
*The scientists wants to provide an individual entry point to his research stored in the repository, aligned with personal information, a personal link collection and the possibility to upload content, e.g. photos, pdfs or movies. | *The scientists wants to provide an individual entry point to his research stored in the repository, aligned with personal information, a personal link collection and the possibility to upload content, e.g. photos, pdfs or movies. | ||
*The public user has found an interesting publication and wants to see more publications of the author | *The public user has found an interesting publication and wants to see more publications of the author. | ||
*The public user has found an interesting publication and wants to contact the author for more details. | *The public user has found an interesting publication and wants to contact the author for more details. | ||
=Functional Specification= | |||
= | |||
==UC Generate researcher portfolio== | ==UC Generate researcher portfolio== | ||
'''Status: in specification''' | '''Status: in specification''' | ||
'''Schedule: ''' | '''Schedule: R5''' | ||
*Condition: The person related to a publication must have person ID to provide researcher portfolio. | |||
*Researcher portfolio is generated on demand, by searching for User ID | |||
*Searching by User Id can be done via Advanced Search or Search&Output. | |||
*The query returns all released publications related to the provided person ID. | |||
*An XSLT is applied to the results and generates a standard layout of publication list,including the personal information of the author (see below data structure) | |||
*The photo is stored externally and integrated (?). | |||
*Provision of pre-defined pre-defined [[PubMan_Feeding_local_webpages#Local_tags | Local tags]]can be used for standard categorization of publications. | |||
Open: Is the researcher portfolio generated on demand (see below, view researcher portfolio) or is it generated as a separate object, with persistent ID? | |||
==UC View researcher portfolio== | ==UC View researcher portfolio== | ||
'''Status: in specification''' | '''Status: in specification''' | ||
'''Schedule: ''' | '''Schedule: R5''' | ||
*"view profile" should be offered for any person which is stored with PersonID | *"view profile" should be offered for any person which is stored with PersonID | ||
*should list all publications related to this PersonID | *should list all publications related to this PersonID | ||
*Can be triggered from detailed item view | |||
==Data structure== | ==Data structure== | ||
| Line 50: | Line 43: | ||
*Organizational unit (controlled) | *Organizational unit (controlled) | ||
*Other affiliations (free text) | *Other affiliations (free text) | ||
=Future development= | |||
*Provide functionality to define own layout of researcher portfolio | |||
*Search within researcher portfolio | |||
*The scientist wants to modify and update his portfolio. He wants to have easy possibility to organize the content on his portfolio and to decide on the structuring keywords. | |||
=Tools= | =Tools= | ||
Revision as of 11:30, 19 November 2008
Scenarios[edit]
- The scientists wants to provide an individual entry point to his research stored in the repository, aligned with personal information, a personal link collection and the possibility to upload content, e.g. photos, pdfs or movies.
- The public user has found an interesting publication and wants to see more publications of the author.
- The public user has found an interesting publication and wants to contact the author for more details.
Functional Specification[edit]
UC Generate researcher portfolio[edit]
Status: in specification
Schedule: R5
- Condition: The person related to a publication must have person ID to provide researcher portfolio.
- Researcher portfolio is generated on demand, by searching for User ID
- Searching by User Id can be done via Advanced Search or Search&Output.
- The query returns all released publications related to the provided person ID.
- An XSLT is applied to the results and generates a standard layout of publication list,including the personal information of the author (see below data structure)
- The photo is stored externally and integrated (?).
- Provision of pre-defined pre-defined Local tagscan be used for standard categorization of publications.
Open: Is the researcher portfolio generated on demand (see below, view researcher portfolio) or is it generated as a separate object, with persistent ID?
UC View researcher portfolio[edit]
Status: in specification
Schedule: R5
- "view profile" should be offered for any person which is stored with PersonID
- should list all publications related to this PersonID
- Can be triggered from detailed item view
Data structure[edit]
Following information should be available on a researcher portfolio, based on the Person ID and the Named Entity Service:
- Photo (stored externally)
- local/internal ResearcherID (once), including URI
- external ID (multiple), including URI if available
- Keywords of research fields (free text)
- Position (title)(controlled list?)
- PhD, year
- Awards (free text field)
- Organizational unit (controlled)
- Other affiliations (free text)
Future development[edit]
- Provide functionality to define own layout of researcher portfolio
- Search within researcher portfolio
- The scientist wants to modify and update his portfolio. He wants to have easy possibility to organize the content on his portfolio and to decide on the structuring keywords.
Tools[edit]
- SelectedWorks web-service, Berkeley
- VITRO ontology editor, Cornell
- Any blog software? (see Discussion page)
- ISI's HighlyCited.com or ISI's researcherID