ESciDoc Committer Meeting 2010-03-02

Date: 02.03.2010 Start time: 14:30

Location: Karlsruhe, München (VidConf) phone: +49-89-38602-223

Participants MPDL: Natasa Bulatovic, Wilhelm Frank

Participants FIZ: Frank Schwichtenberg, Steffen Wagner, Dr. Michael Hoppe, Harald Kappus

Previous committer meeting
 * ESciDoc_Committer_Meeting_2010-02-23

Next committer meetings
 * ESciDoc_Committer_Meeting_2010-03-23
 * ESciDoc_Committer_Meeting_2010-03-30

=Topics=

Core service 1.2

 * RC vs Stable release
 * Test results from MPDL expected

outcome

 * Migration does not work, other methods are fine
 * User groups/ user management - no blocker
 * MPDL will send report of what is tested
 * regarding Administrator-user groups - feedback from MPDL expected

Transfer Ownership

 * see Issue INFR-800 (https://www.escidoc.org/jira/browse/INFR-800)
 * would this be part of 1.3 release?

Outcome

 * planned to improve
 * 1.3 is not yet approved and final
 * consider at least schema/policies change with the interface change in 1.3

PREMIS1 to PREMIS2

 * Steps
 * event types (done)
 * see eSciDoc Version History Event Type and related discussion.
 * resource identifier types see discussion on identifier types
 * user defined comments in versions
 * discuss proposal where/how to set the version comment
 * See PREMIS2 Version history specification and related discussion
 * schedule
 * see also API changes 1.3 (item.xml, settable attributes, version comment)

new properties for OU

 * Discuss/agree on proposal
 * see http://colab.mpdl.mpg.de/mediawiki/Talk:PubMan_History_of_affiliations

outcome

 * not discussed

OAI-PMH Provider and DC Transformation

 * inclusion of version PID and/or object PID in DC datastream in effective manner
 * Coreservice URL as OAI-PMH identifier

Outcome

 * Core service URL
 * according the OAI-PMH specification the identifier of OAI-PMH can not be the OAi-PMH Repository identifier
 * also fedora-identifiers given to OAI-pMH are different
 * dc:identifiers
 * Handle is persistent
 * URL is not persistent in eSciDoc
 * we have to guarantee the URLs
 * technical issues with the eSciDoc XML Export
 * no obvious solution at the moment
 * at the moment DC transformation works only for one single(mandatory) metadata record
 * initial requirement: DC transformation shall work for the Item.xml representation
 * Colab Page for discussion see OAI_PMH_Provider and DC Transformation

Core-service 1.3

 * start?


 * Agreed on joint teams

SolR/Administrative searches/DB cache

 * aspects performance, authorization
 * improvements:
 * facets, tag clouds
 * date searches

Admin tools

 * policies
 * roles
 * AA as potential reuse for non-core service AA (?)

Outcome

 * MPDL prios to be communicated
 * 1.3 feature list not yet confirmed

releases PubMan

 * MPDL can build PubMan 6.0.1 with core-service 1.2
 * Drawbacks:
 * no guarantees (not tested)
 * eSciDoc Admin solution will not run stable
 * expected fully tested 6.1 pubMan Release
 * Mid April 2010

outcome

 * Pubman can be delivered with core-service 1.2
 * need to be tested manually
 * no automated full GUI test coverage so far

Additional Core service questions

 * can statistical service run independently
 * can databases needed for core-service functionality (escidoc-core, statistics, fedora) be configured under completely separate postmasters

outcome

 * statistical service at the moment uses Fedora generated IDs for report/aggregation definition, but it is not impossible (to be placed in JIRA as an impovement)
 * no, they have to run under same postmaster (?)

others

 * eSciDoc-Colab Page setup
 * Alignment of tools and processes (e.g., Maven)
 * Improved and harmonized communication of eSciDoc
 * eSciDoc Blog
 * service names and classification
 * service-architecture board
 * documentation of services
 * installation guides
 * eSciDoc Lab: Colab page gathering experimental modules
 * Exchange of staff members for specific developments or share development

eSciDoc Colab

 * domain-redirection for the eSciDoc-colab
 * set up the colab and move the eSciDoc pages from MPDL colab

Outcome

 * MPDL can not do it until new SysAdmin is on board