Revision as of 17:46, 15 December 2008

Scenarios[edit]

The scientists wants to provide an individual entry point to his research stored in the repository, aligned with personal information.

The public user has found an interesting publication and wants to see more publications of the author.

Status: in specification

Schedule: R4.1

can be triggered from detailed item view (e.g. info icon for each person that has Person ID)
Condition: The person related to a publication must have an authorized CONE person ID to provide researcher portfolio
Researcher portfolio is generated on demand, by searching all publications related to this CONE Person ID
The query returns all released publications related to the person ID.
An XSLT is applied to the results and generates a standard layout of publication list,including the personal information of the person as stored in the CONE service .
The user can query external name authority services when viewing the profile (look-up services for Kaken, WorldCat, ResearcherID, PND)
The external photo is integrated by URL.
The Publication list rendered is sorted by most-recent date, descending.

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, upload content.
Contact author (when visiting the researcher profile, link to email. check for spam/hacks)

@@ Line 24: / Line 24: @@
 =Technical specification=
-==Data structure==
-Following information should be available on a researcher portfolio, based on the Person ID and the Named Entity Service:
-*Photo (stored externally, provided by URL)
-*eSciDoc CONE ResearcherID (once), including URI
-*external ID (multiple), including URI if available. E.g. from KAKEN
-*Keywords of research fields and interests (free text)(no controlled categories)
-*Subject (DDC)
-*Degree (freetext) (e.g.: PhD in Library Science, 2006)
-*Current position (freetext) (e.g. Head of Library)
-*Awards (free text field)
-*Organizational unit (controlled, fetched by OUtree)
-*Other affiliations (free text, e.g. Member of IEEE, Fellow student at xy)
-TODO:
-*Align data structure with requirements from ICE
-*Align with [[Talk:Service_for_Control_of_Named_Entities#Person |proposal for person metadata]]
 =Future development=