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.

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 author (see below data structure)
• The photo is stored externally and integrated (?).

I think with NIMS we have agreed that we enable them to upload a photo--Natasa 12:45, 19 November 2008 (UTC)

• Provision of pre-defined Local tags can be used for standard categorization of publications.

UC View publications

Status: in specification

Schedule: R5

• "view publications" should be offered for publications related to any person which is stored with PersonID
• User triggers "view publications of this author"
• All released Publications related to this AuthorID are searches and displayed on PubMan.

UC View researcher portfolio

Status: in specification

Schedule: R5

• "view profile" should be offered for any person which is stored with PersonID
• can be triggered from detailed item view (info icon with 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)
  • externally here means NIMS server or means external to our Cone store?--Natasa 12:46, 19 November 2008 (UTC)
• local/internal ResearcherID (once), including URI
• external ID (multiple), including URI if available
• Keywords of research fields and interests (free text)

  Controlled categories additionally? e.g. http://www.mpg.de/forschungsgebiete/index.html

• Position (title)(controlled list?)
• PhD, year
• Awards (free text field)

  What's about further information, like memberships, grants, etc?

• Organizational unit (controlled)
• Other affiliations (free text)
• Author e-mail? (to be checked with NIMS)

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.

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

National Institute for Materials Science Japan

Coordinated Universal Time

Publication Management

Uniform Resource Identifier

philosophiae doctor