Difference between revisions of "Pubman Func Spec Researcher Portfolio"

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


*The public user has found an interesting publication and wants to see more publications of the author.
*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=
=Functional Specification=
==UC Generate researcher portfolio==
==UC View researcher portfolio/profile==
'''Status: in specification'''  
'''Status: implemented'''  
 
'''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--[[User:Natasab|Natasa]] 12:45, 19 November 2008 (UTC)
*Provision of pre-defined  [[PubMan_Feeding_local_webpages#Local_tags | Local tags]] can be used for standard categorization of publications.


==UC Search by name==
'''Schedule: R4.1'''
'''Status: in specification'''  


'''Schedule: R5'''
*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


*For any name stored in the system, user can trigger "search for this name".  
[[Control_of_named_entities_-_Persons#Data_structure_detailed_.28authorized_persons_only.29| Data structure]] supported by CONE
*It always seachers by name, even if Author ID is included.
*If results is not sufficient, might be an option, to after search for aliases based on author IDS.


*Result: Search result on PubMan, all releases publications.
*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]] .


==UC View researcher portfolio==
*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)
'''Status: in specification'''


'''Schedule: R5'''
*The external photo is integrated by URL.


*"view profile" should be offered for any person which is stored with PersonID
*The Publication list rendered is sorted by most-recent date, descending.
*can be triggered from detailed item view (info icon with each person that has Person ID)
*this will link to generated researcher portfolio, see [[Researcher_Portfolio#UC_Generate_researcher_portfolio|UC Generate researcher portfolio]]


=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)
* 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.  
**externally here means NIMS server or means external to our Cone store?--[[User:Natasab|Natasa]] 12:46, 19 November 2008 (UTC)
* NIMS wants it to be visible on the researcher profile who last modified it and when.
*local/internal ResearcherID (once), including URI
* There will be an alphabetic sorting for the displayed org units (if a person belongs to more than one org unit).
*external ID (multiple), including URI if available
[[Control_of_named_entities_-_Persons#Comments| Comments on data structure]]
*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)
*e-mail


=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)
*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 69: 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]