Hi, Thank you very much, Ralf, for adding me to the loop.
A few years ago I developed a component for Camel [1] to download meta-information from some OAI-PMH repositories. That was a partial work I had to develop in the European project DrInventor [2]. Since then I haven't worked on that component again but I would be happy to take up the work again to fix possible bugs, add new functionality and update what was needed. If you think it's a good starting point we can start from that content and move on. Regards [1] - https://github.com/cbadenes/camel-oaipmh <https://github.com/cbadenes/camel-oaipmh> [2] - http://drinventor.eu <http://drinventor.eu/> Carlos Badenes-Olmedo cbade...@gmail.com cbadenes.github.io <http://cbadenes.github.io/> > On 10 Mar 2020, at 10:45, Ralf Claussnitzer > <ralf.claussnit...@slub-dresden.de> wrote: > > Hi, > > I made the original developer of the old OAI-PMH library (Carlos > Badenes-Olmedo) aware of the discussion here. He showed interest in further > developing the component but he did not yet join the discussion so I put him > in BCC. > > @Carlos: Please consider registering for the mailing list. Maybe we can sort > out the issues or even rewrite the component to current standards. > >> Alternatively, there are other standards that are not still implemented in >> Apache Camel and they are used in libraries world-wide such as >> MARC21/MARCXML [1] or Z39.50 [2]. > I can confirm. These are widly used in the library data space. But I think > MARC21/MARCXML transformation does not need a component. > > Another (ancient) library standard is SRU [1]. That one could use a component > too. > > [1] https://www.loc.gov/standards/sru/ > > Regards, > Ralf > > On 3/10/20 10:23 AM, Denis Istomin wrote: >> Hello Juan, >> I think it would be great idea to implement new camel-oai-pmh >> component with all features support (that you mentioned) including >> docs, examples, OSGI support etc. >> Also I think it would be useful to have specific example project that >> uses OAI-PMH (based on your expierence in university) [0]. >> >> By the way, you could implement multiple components/tasks during GSoC [1] >> Maybe you could start to write a proposal [2]. >> >> [0] https://github.com/apache/camel-examples >> [1] >> https://issues.apache.org/jira/browse/CAMEL-14625?jql=project%20%3D%20CAMEL%20AND%20labels%20%3D%20gsoc2020%20AND%20assignee%20in%20(EMPTY) >> [2] https://google.github.io/gsocguides/student/writing-a-proposal >> -- >> Denis Istomin >> >> On Tue, Mar 10, 2020 at 3:17 AM Juan Segarra <juanksegar...@gmail.com> wrote: >>> Hi all, >>> >>> I was not aware of the existence of that project [0], thanks for the >>> information. I think that there some details to take into account. >>> >>> - The project is licensed under GPL 3.0, I do not know if there is any >>> conflict with the Apache Licence. >>> - Even though the the last realease was a few months ago, the last commits >>> were made 4 years ago. >>> - Some features such as: GetRecord, ListSets are not implemented yet. >>> - Only the oai_dc metadata format seems to be supported, since there are >>> not schema definitions for other formats such as: xoai or rdf. >>> - It seems that it needs some minor changes to work, I downloaded the code >>> and tried to run it, but obtained some errors in the xjc goal of the >>> jaxb2-maven-plugin that need to be reviewed. >>> >>> I would like to know your opinion about this. On one hand, I could port >>> this project to the Apache Camel codebase (under the creator permission >>> obviously) and implement all missing features, On the other hand, I could >>> implement a new OAI-PMH component from scratch in order to not interfere >>> with this project. >>> >>> Alternatively, there are other standards that are not still implemented in >>> Apache Camel and they are used in libraries world-wide such as >>> MARC21/MARCXML [1] or Z39.50 [2]. There are also good options to be Apache >>> Camel Components and I have some experience working with them. So, I could >>> to create a proposal for them instead. >>> >>> Please let me known your thoughts about this. >>> >>> [0] https://github.com/cbadenes/camel-oaipmh >>> [1] https://en.wikipedia.org/wiki/MARC_standards >>> [2] https://en.wikipedia.org/wiki/Z39.50 >>> >>> Best regards >>> Juan >>> >>> El vie., 6 mar. 2020 a las 3:45, Andrea Cosentino (<anco...@gmail.com>) >>> escribió: >>> >>>> Hello Juan, >>>> >>>> The proposal looks interesting to me. Maybe you can write down your >>>> proposal to submit for Gsoc. >>>> >>>> Il giorno gio 5 mar 2020 alle ore 05:56 Juan Segarra < >>>> juanksegar...@gmail.com> ha scritto: >>>> >>>>> Hi all, >>>>> >>>>> I am Juan Carlos Segarra a student at UDC in Ecuador. I am looking >>>> forward >>>>> to participate as a GSoC student this year. I have some experience >>>> working >>>>> with Java, Maven and Git, and I am familiar with Apache Camel because I >>>>> used it during an internship last year at my university. >>>>> >>>>> In that internship, we tried to integrate some digital repositories, >>>>> digital libraries and other sources of my university using only Apache >>>>> Camel, however as we found out, Apache Camel currently does not support >>>> the >>>>> OAI-PMH [0] protocol for harvesting that kind of data. So, we had to >>>>> develop a workaround with third-party software. Therefore, I thought I >>>>> could propose the implementation of a consumer component for OAI-PMH to >>>> the >>>>> Apache Camel Community. I think that such component will be extremely >>>>> useful for people working with digital repositories and data integration >>>> in >>>>> libraries world-wide. >>>>> >>>>> Please, let me known if you find my proposal interesting for Apache Camel >>>>> and if somebody would be interested in mentoring this, so I can work on a >>>>> formal proposal. >>>>> >>>>> [0] https://www.openarchives.org/pmh/ >>>>> >>>>> Regards, >>>>> Juan >>>>>