MPDL NIMS Developer Meeting 2009-08-25

MPDL,ESciDoc,NIMS

Videoconference with NIMS on 25th of august 2009

Participants: Masao, Mikiko, Michael, Ulla

Last Meeting: Visit NIMS@MPDL

Next Meeting: MPDL NIMS Developer Meeting 2009-10-06

Statistics

 * usage of log data by NIMS? (see mail from Markus Haarländer from 19th august 2009)
 * which aggregations needed? Are current logs sufficient?
 * aggregation by MPDL or NIMS?
 * Visualization of aggregations by NIMS or MPDL?
 * access for MPDL to NIMS-AWSTATS for testing?

Outcome

 * NIMS is visualizing PubMan logs (sent by daily mail) with AWStats, Masao will check data from Markus
 * Aggregated item statistics are done, individual item visualization is in progress
 * see here http://kagaku.nims.go.jp/escidoc/statistics/ (PW per mail)
 * As NIMS is analyzing low-level access log files, MPDL will need to rework
 * CRITICAL: AWStats items stats visualization need to be linked from PubMan-view statistics page
 * "show details" context-dependent (only NIMS items)
 * User needs to login on NIMS server
 * linking to the researchers statistics
 * Should be implemented until 10th of Nov. for Mikiko to show on Library Meeting

Virtual Server

 * Status Virtual Server for Nihon University
 * Servers are set up here http://nims.mpdl.mpg.de/ (current PubMan 5.0.) and http://nims-coreservice.mpdl.mpg.de:8080/ (eSciDoc 1.1.)
 * clarify usage (live? test?) and necessary configs
 * User/context/Workflow configuration by MPDL or NIMS? To be decided if NIMS needs access to nims-admin solution. Server is available.
 * Check for Plan B if needed

Outcome

 * Will be productive environment for Nihon University (4 researchers)
 * NIMS will do the administration on behalf of Nihon
 * MPDL pubman-support to support Nihon users
 * NIMS will inform on OUstructure, context/Workflow, users
 * Should be named escidoc.jp (NIMS will register the domain)
 * CRITICAL todo :
 * Lars will check for admin account for NIMS (urgent!)
 * Check backup strategy
 * Check PID assignment

FACES

 * ingest of Diamond items not before Bastien is back (Sept)

Outcome

 * Generic Faces solution is not finalized yet
 * NIMS delivered 4 sets of images in March
 * CRITICAL:
 * Is end of September feasible for MPDL, to deliver 4 sets including corresponding entry points? Estimated Release date needs to be communicated to NIMS.
 * Do we need to get more info on entry points, GUI, 4 albums or 4 collections etc.? (to check with Bastien, Natasa, Rupert, Kristina
 * MPDL will send prototype examples for the new GUI (prototype proposals current under revision by Malte)

Institutional view

 * define groups for restricted access - explain current functionality
 * 1200 NIMS staff for NIMS-restricted access, i.e. 1200 NIMS user accounts for PubMan
 * Wait for Shibboleth vs. Scripting

Outcome

 * CRICITAL: Scripting needed to mass-import the accounts. Functionality has to work asap, herefore Shibboleth will come too late.
 * MPDL will check what data is needed for batch creation of user accounts
 * Test runs on dev.
 * NIMS will be responsible for user support
 * MPDL to check if access for NIMS to admin-solution
 * Update from Malte after visit@Tsukuba: For the 1200 users, one functional user account will be created, to provide access to NIMS-restricted material--Ulla 10:55, 21 September 2009 (UTC)

Planning

 * BugFix Release 5.0.4 September
 * Metadata Release 6.0. September
 * Switch to Handles on live and test servers September
 * (Functional) Release 6.1.: preliminary planning Feb/March 2010
 * Embargo: no automatic change of access level, but context setting or user preference. Not scheduled yet. Filtering for embargo items in Workspace scheduled for 6.1.
 * CrossRef: Implementation of mapping ("Fetch from CrossRef") scheduled for 6.1. No changing of owner of items, but setting RSS feed for released items for author on Portfolio.

Outcome

 * CRITICAL: "Fetch from CrossRef" in Feb/March too late for NIMS
 * CRITICAL: Corresponding feature "Change of ownership"(or equivalent functionality) is crucial for NIMS:
 * Scientists should be able to modify data that is imported by somebody else
 * Work around: Standard workflow with the scientist being a moderator.
 * Somebody imports the data from CrossRef (as depositor)
 * Scientist can enrich and modify the data (as moderator)