ESciDoc Committer Meeting 2010-03-30

Date: 30.03.2010 Start time: 14:30

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

Participants MPDL: Natasa Bulatovic, Michael Franke

Participants FIZ: Dr. Michael Hoppe, Harald Kappus

Previous committer meeting
 * ESciDoc_Committer_Meeting_2010-03-02

Next committer meetings
 * ESciDoc_Committer_Meeting_2010-04-06 postponed
 * ESciDoc_Committer_Meeting_2010-04-13

=Topics=

new properties for OU

 * see http://colab.mpdl.mpg.de/mediawiki/Talk:PubMan_History_of_affiliations

outcome

 * questions on searching for predecessors/successors
 * items should not be indexed with info on pred/succ
 * when a search for all items of an OU and all of its predecessors is run:
 * pass 1 (by client): give all predecessors of an OU
 * pass2 (by client): give all items with OUs in (OU, OU predecessors)


 * questions on parent/child
 * if structure is changed path in item index will be only changed if the item is changed

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
 * Colab Page for discussion see OAI_PMH_Provider and DC Transformation

outcome

 * check possibility in 1.2
 * transformation works for single metadata record
 * offered as a resource
 * given to content model


 * Core service URL will not bein OAI-PMH identifier
 * core-service URL contain internal identifier

Mime Types and management

 * https://www.escidoc.org/jira/browse/INFR-847
 * consequences in PubMan - differences between CoNE, core-service list, IANA
 * immediate steps: CoNE MimeTypes will be synchronized with core-service list mime types if possible
 * organizational: who will be responsible? (CoNE to be public source, fetched from core-service on regular basis? - core service MIME-updates etc.)

Outcome

 * single list -> maintained by MPDl
 * content models may have restrictions, but independently on CoNE
 * CoNE can be used only for data entry

Status of Heap Space Problem in Pubman Production environment

 * Solved?

outcome

 * problem was in application logic, delivers a lot of results
 * another problem has opened which was the initial cause e.g. searching for

"escidoc.publication.object-type='item' AND escidoc.publication.subject=\& and escidoc.publication.content-model.objid=X " actually cuts the query completely after "\&" and it makes a query on escidoc.publication.object-type='item'

migration to coreservice 1.2

 * Status (?) - potentially from MPDL

Core-service 1.3

 * status
 * priorities from MPDL
 * Requirements for Administrative Search (see comment on https://www.escidoc.org/jira/browse/INFR-727)
 * input after VidCOnf: discussion continued at eSciDoc Administrative search

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
 * documentation of services
 * installation guides
 * eSciDoc Lab: Colab page gathering experimental modules
 * Exchange of staff members for specific developments or share development