Difference between revisions of "Pubman Func Spec Researcher Portfolio"

From MPDLMediaWiki
Jump to navigation Jump to search
 
(39 intermediate revisions by 8 users not shown)
Line 7: Line 7:


=Functional Specification=
=Functional Specification=
==UC Generate researcher portfolio==
==UC View researcher portfolio/profile==
'''Status: in specification'''  
'''Status: implemented'''  


'''Schedule: R4.1'''
'''Schedule: R4.1'''


*Condition: The person related to a publication must have [[Control_of_named_entities_-_Persons |person ID]] to provide researcher portfolio.
*can be triggered from view item version (e.g. icon), with the condition, that the person related to a publication must have an authorized CONE [[Control_of_named_entities_-_Persons |person ID]] to provide his 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 [http://pubman.mpdl.mpg.de/cone/jquery/explain CONE].
*The external photo is integrated by URL.
*The Publication list rendered is sorted by most-recent date, descending.


==UC Search by name==
[[Control_of_named_entities_-_Persons#Data_structure_detailed_.28authorized_persons_only.29| Data structure]] supported by CONE
'''Status: in specification'''


'''Schedule: R4.1.'''
*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.  
*A standard layout of publication list is shown,including the personal information of the person as stored in the [[Service_for_Control_of_Named_Entities | CONE service]] .


*can be triggered from advanced search, qucik search and view item version (author name)
*The user can query external name authority services when viewing the profile (look-up services for Kaken, WorldCat, [http://www.researcherid.com ResearcherID], [http://www.d-nb.de/standardisierung/normdateien/pnd.htm PND], Google Scholar)
*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


*The external photo is integrated by URL.


*The Publication list rendered is sorted by most-recent date, descending.


=Technical specification=
===Comments===
==Data structure==
*The presentation of the researcher portfolio will be in the CONE Service, as this portfolio may contain informations from various escidoc solutions (at the moment only from PubMan).
Following information should be available on a researcher portfolio, based on the Person ID and the Named Entity Service:
*The GUI (css) of the researcher portfolio presentation should be escidoc specific, but well distinguishable from PubMan.
*Photo (stored externally, provided by URL)
* The presentation of the researcher portfolio will be in English, an extra page in CONE service will be needed to provide a translation of the researcher portfolio in e.g. japanese letters.
*eSciDoc CONE ResearcherID (once), including URI
* NIMS wants it to be visible on the researcher profile who last modified it and when.
*external ID (multiple), including URI if available. E.g. from KAKEN
* There will be an alphabetic sorting for the displayed org units (if a person belongs to more than one org unit).
*Keywords of research fields and interests (free text)(no controlled categories)
[[Control_of_named_entities_-_Persons#Comments| Comments on data structure]]
*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=
=Future development=
*Provide functionality to define own layout of researcher portfolio
*Provide functionality to define own layout of researcher portfolio
*Search within 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.
*The scientist wants to modify and update his portfolio. He wants to have easy possibility to organize the content on his portfolio, upload content, remove or add certain publications, re-arrange them.
*Contact author (when visiting the researcher profile, link to email. check for spam/hacks)
*Contact author (when visiting the researcher profile, link to email. check for spam/hacks)
*Propsal: social bookmarking services for researcher portfolio--[[User:Kleinfercher|Kleinfercher]] 07:59, 15 January 2009 (UTC)
*Export the researcher portfolio in FOAF profile
*Provide internationalized researcher portfolios (e.g. in Japanese)
*Provide information on researcher portfolio on who/when last modification (requirement NIMS)


=Tools=
=Tools/Examples=


*[http://works.bepress.com/ SelectedWorks web-service, Berkeley]
*[http://works.bepress.com/ SelectedWorks web-service, Berkeley]
Line 67: Line 52:
*[http://myprofile.cos.com/rkornbluth Community of Science, COS]
*[http://myprofile.cos.com/rkornbluth Community of Science, COS]
*[http://www.epernicus.com/pc Epernicus] - a profile in a social networking tool
*[http://www.epernicus.com/pc Epernicus] - a profile in a social networking tool
*[https://urresearch.rochester.edu/researcher?action=viewResearcherPage&researcherId=3 Example Researcher Page based on Dspace]




[[Category:PubMan|Researcher Portfolio]]
[[Category:PubMan_Functional_Specification|Researcher Portfolio]]
[[Category:Functional_specification|PubMan Researcher Portfolio]]

Latest revision as of 09:04, 16 December 2011

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.
  • The public user is interested in the researcher portfolio of a specific author.

Functional Specification[edit]

UC View researcher portfolio/profile[edit]

Status: implemented

Schedule: R4.1

  • can be triggered from view item version (e.g. icon), with the condition, that the person related to a publication must have an authorized CONE person ID to provide his researcher portfolio

Data structure supported by CONE

  • 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.
  • A standard layout of publication list is shown,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, Google Scholar)
  • The external photo is integrated by URL.
  • The Publication list rendered is sorted by most-recent date, descending.

Comments[edit]

  • The presentation of the researcher portfolio will be in the CONE Service, as this portfolio may contain informations from various escidoc solutions (at the moment only from PubMan).
  • The GUI (css) of the researcher portfolio presentation should be escidoc specific, but well distinguishable from PubMan.
  • The presentation of the researcher portfolio will be in English, an extra page in CONE service will be needed to provide a translation of the researcher portfolio in e.g. japanese letters.
  • NIMS wants it to be visible on the researcher profile who last modified it and when.
  • There will be an alphabetic sorting for the displayed org units (if a person belongs to more than one org unit).

Comments on data structure

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, upload content, remove or add certain publications, re-arrange them.
  • Contact author (when visiting the researcher profile, link to email. check for spam/hacks)
  • Propsal: social bookmarking services for researcher portfolio--Kleinfercher 07:59, 15 January 2009 (UTC)
  • Export the researcher portfolio in FOAF profile
  • Provide internationalized researcher portfolios (e.g. in Japanese)
  • Provide information on researcher portfolio on who/when last modification (requirement NIMS)

Tools/Examples[edit]

Use Case

Control of Named Entities

Identifier

Uniform Resource Locator

Publication Management

Graphical User Interface

National Institute for Materials Science Japan

Coordinated Universal Time

Friend of a Friend Project

Retrieved from "https://colab.mpdl.mpg.de/mw010/index.php?title=Pubman_Func_Spec_Researcher_Portfolio&oldid=73420"