<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="en-BE" link="blue" vlink="purple" style="word-wrap:break-word"> <div class="WordSection1"> I’ve started a new Catmandu branch to focus the documentation more on the command line capabilities. The Perl API I’ve moved to a separate POD file <a href="https://github.com/LibreCat/Catmandu/tree/pr/cmd-line-focus">https://github.com/LibreCat/Catmandu/tree/pr/cmd-line-focus</a><o:p></o:p> <o:p> </o:p> The idea is not to deprecrate things from the core module, but make a transition possible in the future. We feel we are stuck when we keep promoting the Perl API and have to make hard promises nothing will change there. If the usage of Perl is easy as import->each() not harm will be done. But when using all the tricks it makes it too hard for a small team to keep up with that.<o:p></o:p> <o:p> </o:p> As for the none-core modules: I’ve today archived the modules that are really not maintained for many years anymore and will not be maintained in the future:<o:p></o:p> <o:p> </o:p> Catmandu-AWS Catmandu-EAD Catmandu-MediaMosa Catmandu-ORCID Catmandu-Store-CouchDB Catmandu-Twitter<o:p></o:p> Catmandu-ArchivesSpace Catmandu-Geocode Catmandu-Mendeley Catmandu-R Catmandu-Store-Lucy <o:p></o:p> Catmandu-Cmd-fuse Catmandu-Hadoop Catmandu-OCLC Catmandu-Store-CHI Catmandu-Tests What we keep is all the modules that do format conversions. I’ve put Catmandu::EAD here because the Catmandu::XSD is a more powerful option.<o:p></o:p> <o:p> </o:p> As I understand we all have roughly the same idea that Catmandu shouldn’t try to solve every ETL problem but do what it does best: focusing on library formats and conversions for which there are no better options in the bigger world of ETL in general.<o:p></o:p> <o:p> </o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Patrick Hochstenbach <Patrick.Hochstenbach@UGent.be> Date: Tuesday, 17 January 2023 at 15:42 To: Rolschewski, Johann <Johann.Rolschewski@sbb.spk-berlin.de>, librecat-dev@lists.uni-bielefeld.de <librecat-dev@lists.uni-bielefeld.de> Subject: Re: [librecat-dev] Happy New Year<o:p></o:p> </div> Hello Johann<o:p></o:p> <o:p></o:p> Thanks for the feedback. Yes, there is a link indeed to the wiki pages. It might be bit more nerdy to read, but it contains the same information and is much easier to edit and is always up to date (the LibreCat version was not).<o:p></o:p> <o:p></o:p> I know what I have to do in my next library days for Catmandu projects 😊<o:p></o:p> <o:p></o:p> Patrick<o:p></o:p> <o:p></o:p> <o:p></o:p> <div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm"> From: Rolschewski, Johann <Johann.Rolschewski@sbb.spk-berlin.de> Date: Friday, 13 January 2023 at 10:51 To: Patrick Hochstenbach <Patrick.Hochstenbach@UGent.be>, librecat-dev@lists.uni-bielefeld.de <librecat-dev@lists.uni-bielefeld.de> Subject: AW: [librecat-dev] Happy New Year<o:p></o:p> </div> <div> Hey all, happy New Year! > Best wishes for all of you in 2023. I see we have this year our 10 year > anniversary of publishing open source code for libraries together. I've joined my first Catmandu workshop in 2012 and I really enjoy to work with you all on this project. > Doing all our > ELAG and SWIB meeting we managed to publish 131 repositories at > <a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLibreCat&data=05%7C01%7CPatrick.Hochstenbach%40ugent.be%7C19905f8cf8b94629708408daf54baf05%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C638092002647650115%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PZfcXGXk0D7d0uuDfo2jEiZnzWtYIIy5issS%2B4RTR7s%3D&reserved=0">https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLibreCat&data=05%7C01%7CPatrick.Hochstenbach%40ugent.be%7C19905f8cf8b94629708408daf54baf05%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C638092002647650115%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PZfcXGXk0D7d0uuDfo2jEiZnzWtYIIy5issS%2B4RTR7s%3D&reserved=0</a>. There are few library projects that can repeat > that feat. The core module has 161 stars on Github and 21 ++ on Metacpan, which is really great for a project in the LibIT domain! > I hope we will meet each other soon again in live conferences. I've > very much enjoyed SWIB and ELAG the last 2 years, but it is still much better > with a discussion and a beer and some unhealthy food. I'm also looking forward to see you all in person on the next live conference. If there's any interest I could try to organize another Catmandu workshop in Berlin. > Here is a proposal for a smaller website: > <a href="https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLibreCat%2Flibrecat.github.io%2Ftree%2Fpr%2Fsmaller&data=05%7C01%7CPatrick.Hochstenbach%40ugent.be%7C19905f8cf8b94629708408daf54baf05%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C638092002647650115%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6Bc%2BZWedOLVVnRiQYaVQeix0mmu5LtgMXV36S3xYZ50%3D&reserved=0">https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FLibreCat%2Flibrecat.github.io%2Ftree%2Fpr%2Fsmaller&data=05%7C01%7CPatrick.Hochstenbach%40ugent.be%7C19905f8cf8b94629708408daf54baf05%7Cd7811cdeecef496c8f91a1786241b99c%7C1%7C0%7C638092002647650115%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=6Bc%2BZWedOLVVnRiQYaVQeix0mmu5LtgMXV36S3xYZ50%3D&reserved=0</a> +1 > TODO: could some of you check if this new website is okay for you? One question: the documentation should link to the Github wiki? > What are your thoughts about this: > > * Do you use the command line interface? Yes, we also have internal workshops regularly to train our librarians to use it to preprocess data for cataloguing. > * Do you use the Catmandu.pm Perl libraries inside your code? Do you > write Perl code that requires Catmandu? Yes, but these are mainly small modules/scripts to load data to MongoDB and query it to generate statistics/reports as XLSX files. These could be replaced quite easily. > * What are the main Catmandu extension modules you use > (Catmandu::MARC, Catmandu::DBI, Catmandu::RDF, ...) + Catmandu::Breaker + Catmandu::Identifier + Catmandu::MARC + Catmandu::OAI + Catmandu::PICA + Catmandu::RDF + Catmandu::SRU + Catmandu::Stat + Catmandu::Template + Catmandu::Validator + Catmandu::XLS + Catmandu::XSD + Catmandu::Z3950 > * Do you use Catmandu to store or query data in databases or search > engines? I use MongoDB a lot, but use MongoDB::MongoClient for that. As the MongoDB module is EOL I will move to Postgres or SQLite. I'm in favour to deprecate the Catmandu::Store::* modules. They just offer some basic API functions and I often have to write my own connectors for functions I need. Some stores like MongoDB provide their own command-line interfaces to load, export and query data. Cheers, Johann <o:p></o:p> </div> </div> </body> </html>