MPDL SvM Meeting 2009-02-05

MPDL

PubMan

 * How about styling the PubMan Blog Header like the PubMan Solution? (Perhaps Andi or Kristina can help)--Kleinfercher 10:07, 2 February 2009 (UTC)
 * I had the idea before as well. The problem is, that I don't have time at all. From Kristina I know, that a lot of effort is needed to get the skin fine... --Nicole 12:44, 11 February 2009 (UTC)
 * -OK, so it`s postponed.
 * Outcome of meeting, 11.2.09 with Malte: Is not of high priority at the moment. --Nicole 13:53, 12 February 2009 (UTC)


 * Should we enable import md AND fulltext from escidoc? Problem we do not know in advanced if there is a full text to fetch (other than pubmed or arxiv).--Friederike 08:31, 4 February 2009 (UTC)
 * Don't exactly get the point. What would happen if we would enable to fetch ft from escidoc? --Nicole 12:44, 11 February 2009 (UTC)
 * The problem is that a ft in pubman is optional. If we offer fetch fulltext from escidoc like we do with arxiv, it can happen that the user selects yes, but the item does not have one. This is not a problem for dev at all, but perhaps for func? If its no problem for func, its no problem at all ;)--Friederike 12:50, 11 February 2009 (UTC)
 * Outcome of meeting, 11.2.09 with Malte: fetch of MD and FT will be implemented, interface should explain, that not always a full text is available. --Nicole 13:53, 12 February 2009 (UTC)


 * Short status report and cross check on PubMan welcome page for not logged in users. --Nicole 12:08, 3 February 2009 (UTC)
 * My ideas where now implemented on Dev. by Rike. If someone has other wished/ideas, please inform me. --Nicole 12:44, 11 February 2009 (UTC)
 * Outcome of meeting, 11.2.09 with Malte: Fine with how it is implemented now.


 * Migration of eDoc data on QA last week. A final one on QA will follow when Julia is back. --Nicole 13:26, 11 February 2009 (UTC)
 * Today the new FW is being installed on live server. Users have been informed. In that step the test data, OUs, users of MPIPL are being deleted. Next step is to create new OUs, users and Contexts on Live for MPIPL. --Nicole 13:26, 11 February 2009 (UTC)
 * fist version of PubMan screencast is finished and will be integrated into the new PubMan start page. --Nicole 13:27, 11 February 2009 (UTC)
 * Outcome of meeting, 11.2.09 with Malte: a new microphone should be bought, as the microphone we have doesn't deliver satisfying sound output. For now the video will stay as it is and will be synchronized again when the new mic. has arrived. --Nicole 13:53, 12 February 2009 (UTC)


 * changed CoLab portal and overview pages for single functionalities. PubMan functionalities overview page is finished.--Nicole 13:27, 11 February 2009 (UTC)
 * researcher portfolio:
 * Is there a sorting for displaying the org units in the profile? --Melanie.stetter 14:23, 4 February 2009 (UTC) E-Mail sent to Masao, if KAKEN db does any sorting.
 * They should be ordered alphabetically.


 * Should the eMail adress be displayed (link) or just an eMail button?
 * Order of the fields? (spec needed)
 * CrossRef:--Friederike 14:23, 5 February 2009 (UTC)
 * MPDL has an agreement with crossref which we could use for pubman (1 mio. queries allowed).
 * This account should only be used within the MPDL. (NIMS?).
 * Importsources orgUnit specific??? -- Malte will take care of this, probably we get own agreement for PubMan instances.


 * Account data were provided by Inga.
 * This account has to be activated for the fetching server.
 * Possible Use Cases:
 * Fetch Metadata via doi(pubman import)
 * fetch DOI via md(pubman submission)
 * fetch location/fulltext of item via DOI (pubman submission)
 * Inconsistent mapping:--Friederike 16:35, 10 February 2009 (UTC)
 * mapping is not inconsistent. URL field in BibTeX is used for getting the actual full text and in PubMan the locator is most often used for supplementary material. Therefore I would not vote for mapping the locator and leave the mapping as it is. --Nicole 12:38, 11 February 2009 (UTC)
 * We could map a locator to bibtex url, if the locator.type = fulltext.--Friederike 12:52, 11 February 2009 (UTC)

-- We consider this for future improvement. -- Restart discussion about Resolution/Identifier in DEV Meeting. --Start discussion about custom bibtex export in DEV Meeting.
 * bibtex to escidoc, url is mapped to locator
 * escidoc to bibtex, locator is not mapped
 * Got an answer from CERN, it is NOT possible to fetch Spires data over their OAI Interface, therefor we stick with only SPIRES as import source.--Friederike 12:11, 11 February 2009 (UTC)
 * MD Fetching: should we save the location of an item (e.g.: http://arxiv.org/abs/0902.1526) as an identifier or an locator.--Friederike 12:11, 11 February 2009 (UTC)
 * Include eprint and archivePrefix field in bibtex mapping? (input from arxiv)--Friederike 13:14, 11 February 2009 (UTC)

Pubman extensions
MAB Mapping for MPI EVA

Cluster Jus
 * Cluster Jus-consolidate requirements (Meeting Juliane, Nicole, Ulla 10th of feb, 14:00)

FACES
Release 3.5
 * As release 3 will be presented to the institute in the middle of march, it would be nice to have the GUI prototype ready at the same time
 * Do we need a kick off meeting or shall the GUI just start?
 * Rupert is organizing one. --Kristina 11:25, 10 February 2009 (UTC)
 * Further planning:
 * Will there be a GUI release between R3 and R3.5?
 * No. GUI v2 will mostly be implemented in R3.5. The rest can be done in R4. --Kristina 11:25, 10 February 2009 (UTC)
 * In Jira, release 3.2 was created. This is only for technical reasons. All work concerning surrogate items depends on feedback from FIZ and is not needed for R3. --> was postponed!

VIRR
Requirements
 * Institute wants to distinguish between the inverse form of the name of a creator and the normed form. How can we handle that requirement? E.g. via the integration of an authority file (PND)? Is that possible via the CoNE service?
 * Currently the PND can not be integrated in our services because they do not offer a web interface.
 * We will offer the institute three fields (one for each name form), where they can enter the different name forms.
 * "Edit bibliographical metadata" is not really needed within ViRR (but as I understand them right we can keep it). The institute wants to have a possibility to update the MAB data in their internal system and than upload one MAB file for a whole collection in eSciDoc (if possible by themselves).
 * Editing interface will offer the opportunity to edit all available metadata values
 * Currently we can only offer on button next to the editing interface where the institute can import one MAB data set. But when we can handle mass ingestions in PubMan we can also integrate that into ViRR. TO DO (Kristina): Check if the institute wants to have the button in Release 3 or wait for the mass ingestion.
 * Servers
 * Currently there is no content on the demo server. Wilhelm will start to ingest
 * on qa server (as qa currently works with the content from dev and dev has already changed till the qa release --> problems occur already)
 * on live server (so we can release 2.0 on live)
 * on demo server


 * Planning
 * Based on input from Natasa, the release can be delivered at the end of march. --Kristina 13:11, 11 February 2009 (UTC)

CoLab/TWR/
Other
 * PubMan/ViRR/Admin Solution pages on eSciDoc Homepage
 * central reference to a page, which lists all current functionalities (Blog, Demo, CoLab ... etc.), should be linked on each solution website on www.escidoc.org
 * only main functionalities on eSciDoc-Webseite
 * talked to Kristina and Nicole: list of all current functionalities in CoLab -> new pages for Faces Functionalities, ViRR Functionalities and PubMan Functionalities