Pubman Func Spec Researcher Portfolio

Scenarios

• 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.

• The public user is interested in the researcher portfolio of a specific author.

Functional Specification

UC Generate researcher portfolio

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 of publications related to this Person ID
  • Searching by person 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 person (see below data structure). The person information is stored in CONE.
• The external photo is integrated by URL.
• The Publication list rendered is sorted by most-recent date, descending.

UC Search by name

Status: in specification

Schedule: R5

• For any name stored in the system, user can trigger "search for this name".
• It always searches by name.
• If results is not sufficient, might be an option, to after search for aliases based on personIDs.

• Result: Search result on PubMan, all released publications.

UC View researcher portfolio

Status: in specification

Schedule: R5

• "view portfolio" should be offered for any person which is stored with PersonID
• can be triggered from detailed item view (e.g. info icon for each person that has Person ID)
• this will link to generated researcher portfolio, see UC Generate researcher portfolio

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)

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

Tools

• SelectedWorks web-service, Berkeley
• VITRO ontology editor, Cornell
• Any blog software? (see Discussion page)
• ISI's HighlyCited.com or ISI's researcherID
• Community of Science, COS
• Epernicus - a profile in a social networking tool

Use Case

Identifier

Extensible Stylesheet Language Transformations

Uniform Resource Locator

Publication Management

Enhanced Scientific Documentation

Control of Named Entities

Uniform Resource Identifier

Display Data Channel

philosophiae doctor