NIMS

MPDL,NIMS

Phase 1 (April 2008 - March 2009)

 * see also outcome of NIMS visit January 26-27, 2009

Translation of Resource Bundles

 * Masao - works with the resource bundles

Access to content

 * IP address based access
 * Possibility to provide access to fulltext on organisational unit level
 * See also ESciDoc Institutional visibility.


 * Note: "invitation to external scientists" and "integration of user access in institution level" features are also related to "User access management" in.

Author identifiers

 * needed for auto-profile function (relate publication and person) see example below
 * support for multiple IDs needed (e.g. NIMS employee number)
 * people assigned to more than one department (NIMS and external)

User auto profiling functions

 * Extend current named entity service for persons with desired data structure
 * Proposal for data structure:
 * Photo
 * ResearcherID (NIMS ID)
 * KAKEN ID
 * Personal URL
 * Keywords of research fields
 * Position (title)
 * PhD, year
 * Awards
 * Affiliation
 * Organization name


 * Allow Mikiko to edit demo data
 * Make persons in Person storage accessible by URI(URL)
 * Create Person page for browsing by URL
 * user interface for the person page to be designed in sync with CV management solution
 * new citation style output format (pure html list, no headers)
 * person page is invoking Search&Export for the person and displays list of publications together with person data (see above)
 * Person page will also include list of publications for this person fetched from PubMan
 * Publication list items are clickable and point to PubMan item view
 * 10 scientists demo data needed to get started

See specification under Researcher Portfolio

User usage monitoring functions
Please check the final specification under PubMan Statistics


 * Public usage statistics on items:
 * (available already) Access by item: separate for item and fulltext


 * Private statistics (just for researcher (and moderator)) available from researcher profile page:
 * (new, needs better specification) By nation (based on internet address) or .gov, .com (=type of organisation) => google maps
 * "By nation" is not clear what is meant in here. Issues:
 * (new, needs better specification)Referrers: Track the search request from google, google scholar etc. => to show how popular the search request
 * for above two requirements see also Piwik Web Analytics Reports
 * (new, needs better specification) If internal access in NIMS, identify from which research group (for registered users)=>> not possible currently, as we do not have this information. user handle does not contain information on affiliated organisational unit. IP adresses have to be cut due to data privacy issues. Might be solved partly by user group ID (upcoming in 2009)--Ulla 09:49, 21 November 2008 (UTC)
 * (available alreday) Time scale (dates of access)
 * Data should be presented graphically for easy understanding
 * administrative reports
 * Individual Reports (e.g. total number of items, number of OA, number of access to items…)

Consolidation

 * see also outcome of NIMS visit June 17/18, 2009


 * Automatic Blog generation
 * domain names?
 * who triggers Blog generation?
 * clear workflow for editing/modifying CONE data
 * set name of user and date of last modification for each entity
 * who can edit/modify person data for which organisational unit?
 * who can edit journal names?

New features

 * Rights and embargo
 * First priority, scheduled for R5 (May 2009):
 * "rights statement" (freetext) per item
 * CC-Licenses per component
 * Embargo times per component
 * =>See Specification under PubMan Copyright--Ulla 16:13, 29 January 2009 (UTC)
 * Second Priority (might be tackled in separate MPDL project for "copyright handling workflow")
 * Supportive tools (e.g. link to Romeo/sherpa or SCPJ)
 * Additional "check points" during workflow to verify rights information (by whom? when? which information?)


 * User access management
 * Shibboleth and LDAP integration is available within eSciDoc
 * First priority: Enable LDAP for PubMan
 * Shibboleth infrastructure would have to be setup at NIMS in advance
 * Shibboleth makes use of “eduperson” profile


 * Linking/Fetching functions between items and other providers
 * Fetch MD from CrossRef (see under CrossRef => first priority!
 * => Depends on licensing options and possibilities to store CrossRef data (Malte)
 * => --Ulla 15:42, 16 March 2009 (UTC)alternatively: Improvement of COIN specification and integration of openurl resolver registry?
 * complementary to CRossRef, DOAJ offers small subset of articles which are not available via CrossRef
 * => some DOAJ Journals provide metadata on article-level (see Example for LivRev).
 * DOAJ - OAI Interface


 * Export to junii2 (i.e. DC application profile for scholarly works in japanese repositories. | XSD)
 * See also JuNii2 mapping
 * further mapping by NIMS


 * Shape scenario for Patent management
 * Aim: Patents as part of researcher portfolio, are own objects. Some Patent Metadata include Links to Publications on PubMAn and/or external Publications. Patent MD shoudl be indexed and searchable.
 * NIMS will send Application Profile for Patent data
 * MPDL to check solution by FIZ
 * Patent Data as Cone Data? (Cone@NIMS)
 * Based on final scenario: part of PubMan Solution or own solution, see also [Institutional activities on PubMan]


 * Coverpage for pubman items
 * Aim: Create additional coverpage for publications, which includes some information on rights and the title of the publication and add it to the uploaded PDF. User who downloads the PDF, gets PDF including the Coverpage.
 * Masao will send example Cover page
 * Proposal: Add "Create Cover page for each pdf uploaded" as setting for a context, i.e. is optional for each institute to choose. Original PDF will be stored in addition to new generated PDF, which includes cover page.

Productive system@Japan
JST as possible hosting partner?

FIZ already contacted JST, but no outcome known currently.--Ulla 15:18, 16 March 2009 (UTC)

FACES@NIMS
Aim: Show prototype of FACES with diamond images at eSciDoc Days in June. Most probably, the collection will be publicly available.


 * NIMS sends (basic) Metadata and files
 * application profile will be a preliminary one
 * Do the images have to be manipulated before the ingest, for storing "copyright statement"?
 * permanent credit on image?
 * credit generated when exporting?
 * depends on resolution, zooming needed
 * Ingest of images by MPDL
 * As soon as current R3 is successfully deployed, around end of march
 * Further modifications by NIMS (supported by Bastien Saquet, developer Faces)
 * DigiLib implemented in Core services

Background:
 * Release 3.2. of Faces (MPDL) will focus on generalisation of FACES for any kind of content, but will not be deployed for the eSciDoc days at time.

Phase 3 - tbd
Misc:
 * Access to content
 * Possibility to invite external colleagues to share content of repository (example "LinkedIn")
 * Items in Japanese characters
 * Check with demo data
 * Linking functions between items within eSciDoc
 * Currently just revisions are possible.
 * Structural relations have to be shaped and thought of (e.g. is translation of)
 * Better visualisation needed of related items anyway (search for nn-search result list – see related items as bundles and/or see latest revision first and/or see related OA articles)
 * see also requirements PubMan Pilots - Marion Schmidt
 * Digitisation and publication of library holdings (e.g. project reports)
 * ingestion
 * TOC
 * presentation
 * copyright restrictions (access level NIMs or public)
 * Semantic indexing (faceted search, proximity search) => to provide "Related papers"

Meetings NIMS-eSciDoc

 * June 2009 in Munich and Karlsruhe (eSciDoc Days). Meeting summary see NIMS visit June 17/18, 2009
 * March 6-8, 2009 in Japan, ALIEP at Tsukuba Univ.
 * Januar 2009 NIMS@MPDL, Munich. Meeting memo see NIMS visit January 26-27, 2009
 * November 25, 2008 in Japan, Digital Library Board Meeting at NIMS (15:00pm-)