MPDL NIMS Developer Meeting 2009-06-17

MPDL,ESciDoc,NIMS

Summary of NIMS visit@MPDL Munich, June 17/18 2009

PubMan
New label for “my items”: “my deposits” or “my submissions” (because label is misleading; my items means items I deposited to the system, not items I am the owner of)


 * this might get in conflict with the (future) feature on collaboration => items, where i am allowed to collaborate on, are listed in "My items" as well, but are neither "my depositos" nor "my submissions". Do not understand the last assumptions..."My items" does include items where i am the owner of, i.e. deposited by me (?)--Ulla 18:37, 1 July 2009 (UTC)

sorry, again misleading, what was meant here is that NIMS was confused with the label "my itmes", because they thought, the user is author of all itmes in my items--Melanie.stetter 10:17, 3 July 2009 (UTC)

Statistics (prio high)

 * In addition to logged in/not logged in user one of the following (regarding institutional visibility) should be logged:


 * Author User ID
 * OU ID or
 * Both AuthorUser ID and OU ID


 * Statistics for NIMS based on


 * items
 * persons
 * institutional level


 * New button on statistics page (for NIMS statistics on their server)
 * Masao talk to Markus H. and Natasa
 * NIMS has build a statistics system for pubman on the base of AWStats and JAWStats
 * The system is using the PubMan server logs.
 * MPDL is now trying to log certain information using eSciDoc statistic management, see Talk:PubMan_Statistics
 * NIMS will try to integrate this data into their system in order to get further statistics.

CoNE (prio high)

 * Librarians to check on different name versions (same person?) --> who else?
 * Moderator roles for everyone who feels responsible
 * RDF import is extended to overwrite existing entries when a CoNE ID is given. This enables NIMS to import persons from their database and maintain this list in regular intervals. -- MFranke 08:49, 30 June 2009 (UTC)

Fetching (prio high)

 * CrossRef


 * Nims scenario: query by DOI, fetch metadata
 * Import, multiple import?
 * Mapping needed
 * Workflow for now:


 * User enters list of DOIs
 * Moderator to fetch metadata
 * Moderator to tag item
 * RSS feed for user with info on imported items
 * User to check
 * Collaborator-Modifier role for scientists
 * Moderator to release item


 * Possibilities discussed:


 * New workflow needed?
 * Moderator acts as user (depositor --> with permission of user) to import items
 * Collaborator-Modifier could be “On-behalf-depositor” (ask FIZ)
 * Transfer ownership? (ask FIZ)
 * Separate collection to fetch from CrossRef (no moving between collections)


 * Moderator can deposit pending items into this collection
 * Moderator can give collaboration rights for these items to user (search for pending items; new functionality: search items for resp. user)
 * User can copy items into his/her collection


 * All users items in own collection, owner and other person have moderator and depositor rights
 * Moderator to fetch items, send message to user (RSS) to check if they’re his/hers, deposit into users own workspace so user can be owner/depositor of items (list of HTML/APA exports send to user), tagged items


 * CiNii


 * See outcome CrossRef
 * Mapping needed
 * Masao to talk to Rike

Server structure (prio 1)

 * Virtual server for Nihon University to be set up by MPDL
 * Virtual machine effects logs: handlers needed, no redirect on item level possible
 * Productive system: NIMS stays on our system, waiting for productive system

Embargo Date

 * Release and change of visibility of items, when embargo date is over --> depending on workflow


 * Simple workflow: automatic release after embargo date ends, visibility public
 * Standard workflow: moderator to decide for release after embargo date ends, items in QA workspace to change status

Uploading scanned pdfs

 * NIMS scenario:


 * Scanned conference proceedings
 * One pdf per item
 * Digitized by NIMS
 * Plus readable information
 * No NIMS publications


 * New context with simple workflow --> use NIMS Library context ("Materials Science Library")

Blog

 * For now: Mail to dev-list for creation of new blog
 * Researcher as admin for his/her blog
 * Future development:


 * Button in CoNE to create new blog on demand or
 * Allow creation for logged in users on PubMan blog
 * Nice to have: automatic blog generation

Coverpage

 * Configurated for NIMS collections
 * “Brief” metadata of the item displayed
 * On-the-fly creation when user wants to download the file
 * To be checked--Ulla 07:44, 11 August 2009 (UTC):
 * Only relevant for specific content categories? (e.g. only for author versions?)
 * Only relevant for specific document-types/genre types? (e.g. journal articles only)
 * Include PID/URL on cover page? (see example HAL)

Patent

 * New genre type patent needed
 * Special context for NIMS patents
 * Data to be sent from NIMS

FACES

 * More collections using same metadata scheme as diamonds
 * Masao to send xml file to Bastien