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: R4.1

• 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: R4.1.

• can be triggered from advanced search, qucik search and view item version (author name)
• is not dependent on available ID
• is complementary to "view researcher portfolio"
• If personID available, search for PersonId
• If no personID available, search for name string??
• In advanced search: user can select if searching for exact name on pub?
• Result: Search result on PubMan, all released publications of provided name string/person ID

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 proposal for person metadata

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

Internet Chat Exchange