Re: Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)
Hi, On Tue, Mar 16, 2010 at 11:13 PM, Galen Charlton gmcha...@gmail.com wrote: If there are no major objections, in a week's time I plan to make the CVS repo read-only and we'll move forward with Git. I've now removed write access to the CVS repository, and will disable CVS entirely once I see that people are comfortable pushing commits to the Git repo. Regards, Galen -- Galen Charlton gmcha...@gmail.com
Re: Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)
Hi, On Tue, Jan 26, 2010 at 11:57 AM, Ed Summers e...@pobox.com wrote: I would argue for keeping stuff on sf.net ... and leapfrogging svn for git if we can. To that end, I've enabled Git in the marcpm SourceForge project and established a new repository which contains the history from the five CVS modules (marc-charset, marc-lint, marc-marcmaker, marc-record, marc-www, and marc-xml) merged into one Git repo. Please note that I chose to lump them together since the MARC/Perl modules are fairly interdependent on one another, but if there's a general desire to have a separate Git repo for each of the legacy CVS modules, I can set it up that way instead. The read-only git URL is git://marcpm.git.sourceforge.net/gitroot/marcpm/marcpm The git URL for developers to push to is ssh://yourusern...@marcpm.git.sourceforge.net/gitroot/marcpm/marcpm Everybody who has commit access to the old CVS repositories should have access to push to the Git repository. The Git browse URL is http://marcpm.git.sourceforge.net/git/gitweb.cgi?p=marcpm/marcpm;a=summary For those who need it, numerous Git tutorials are just a web search away, and I'm happy to help anybody who needs a hand getting started with Git - drop me a line or ping me on #code4lib. If there are no major objections, in a week's time I plan to make the CVS repo read-only and we'll move forward with Git. Regards, Galen -- Galen Charlton gmcha...@gmail.com
Re: Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)
On Tue, Mar 16, 2010 at 11:13 PM, Galen Charlton gmcha...@gmail.com wrote: If there are no major objections, in a week's time I plan to make the CVS repo read-only and we'll move forward with Git. Hooray, thanks so much Galen! Sounds like a great plan moving forward. //Ed
Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)
Hi, On Wed, Jul 22, 2009 at 7:53 PM, Dueber, William dueb...@umich.edu wrote: Speaking for myself only, of course: Please, for the love of god, move away from CVS. Moving the code to a more modern VCS and a well-supported host. The least-painful move might be to SVN on Google Code. Picking up on this thread, I'm prepared to go ahead this weekend and get MARC/Perl moved to SVN on Google Code, to give us a modern VCS and a better host while meeting Bryan's request for a VCS that has a Windows front-end. +1/-1? Regards, Galen -- Galen Charlton gmcha...@gmail.com
Re: Moving to Google Code/svn (was Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML)
Hi, On Tue, Jan 26, 2010 at 10:57 AM, Ed Summers e...@pobox.com wrote: I would argue for keeping stuff on sf.net ... and leapfrogging svn for git if we can. Both suggestions would be perfectly fine with me. Bryan, for your reference, TortoiseGit [1] seems to be a well-supported Windows client for Git. [1] http://code.google.com/p/tortoisegit/ Regards, Galen -- Galen Charlton gmcha...@gmail.com
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
Hi, On Wed, Jul 22, 2009 at 5:04 PM, Dan Scottdeni...@gmail.com wrote: Was it decided that Bill's escaping output patch would be dropped? I don't see it in CVS yet. I've committed Bill's patch and a test case based on the sample file he sent. Thanks, Bill! Regards, Galen
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
Was it decided that Bill's escaping output patch would be dropped? I don't see it in CVS yet. It would be nice to see the 0.91 release get pushed out the door, in any case. 0.88 was a long time ago. Dan 2009/4/14 Galen Charlton galen.charl...@liblime.com: Hi, On Tue, Apr 14, 2009 at 3:57 PM, Dan Scott deni...@gmail.com wrote: 2008/10/29 Bill Erickson billserick...@gmail.com: Is anyone planning on applying this patch? It would be a shame to drop it on the floor. I'll take a look at it and apply it, unless somebody beats me to the punch in the next day or two. Regards, Galen -- Galen Charlton VP, Research Development, LibLime galen.charl...@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt -- Dan Scott Laurentian University
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
Hi, Nope, just haven't gotten around to pushing it. Soon, I promise! Funny you should mention CVS. I have a general question for the MARC/Perl hackers: Ed mentioned a while back moving from CVS to a more modern VCS such as Subversion or (my preference) Git. I'm willing to do the legwork to get the repositories moved. Thoughts? Regards, Galen On Wed, Jul 22, 2009 at 5:04 PM, Dan Scottdeni...@gmail.com wrote: Was it decided that Bill's escaping output patch would be dropped? I don't see it in CVS yet. It would be nice to see the 0.91 release get pushed out the door, in any case. 0.88 was a long time ago. Dan 2009/4/14 Galen Charlton galen.charl...@liblime.com: Hi, On Tue, Apr 14, 2009 at 3:57 PM, Dan Scott deni...@gmail.com wrote: 2008/10/29 Bill Erickson billserick...@gmail.com: Is anyone planning on applying this patch? It would be a shame to drop it on the floor. I'll take a look at it and apply it, unless somebody beats me to the punch in the next day or two. Regards, Galen -- Galen Charlton VP, Research Development, LibLime galen.charl...@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt -- Dan Scott Laurentian University -- Galen Charlton VP, Research Development, LibLime galen.charl...@liblime.com p: 1-888-564-2457 x709 skype: gmcharlt
RE: [Patch] Escape marc tag/code/indicators in Marc::File::XML
On Wednesday, July 22, 2009 4:10 PM, Galen Charlton [galen.charl...@liblime.com] wrote: Funny you should mention CVS. I have a general question for the MARC/Perl hackers: Ed mentioned a while back moving from CVS to a more modern VCS such as Subversion or (my preference) Git. I'm willing to do the legwork to get the repositories moved. Thoughts? Speaking as a hobbyist programmer, I've only used CVS, and would hope that a move to a different system wouldn't make it a more complicated or difficult to use system. Until last November, my main development machine was (and still would be) a PowerMac 7500/G3 with MacOS 9. When I tried to update SourceForge CVS this May using my Mac, I believe my SSH login failed (it had worked fine in August 2008), so I switched to updating SourceForge CVS using WinCvs on my Windows Vista laptop (Nov. 2008). I'm not sure what changed to prevent the Mac from being able to get a SSH connection to SourceForge, but I chalked it up to being an age thing (SourceForge update making old operating systems obsolete; or some change to SSH that I couldn't figure out how to fix in the MacSSH client; it does seem like it took a little bit of work getting WinCvs set up, as well), and that from now on, the Windows machine will be what I need to use to be able to update anything on SourceForge. So, as long as there is an easy-to-use Windows-based client for the other version control systems, then I probably wouldn't have a problem with switching. Thank you for your time, Bryan Baldus bryan.bal...@quality-books.com eij...@cpan.org http://home.inwave.com/eija
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
Speaking for myself only, of course: Please, for the love of god, move away from CVS. Moving the code to a more modern VCS and a well-supported host. The least-painful move might be to SVN on Google Code. I'm pretty sure there's nothing but CVS available for OS9, though, so the question has to be whether or not the pain of using CVS on Sourceforge outweighs the potential loss of people stuck on ancient OS's. With apologies to Bryan, I know I'd be a lot more likely to work with the code if it were hosted in a way that made it easier for me to deal with. -Bill- On 7/22/09 8:23 PM, Bryan Baldus bryan.bal...@quality-books.com wrote: On Wednesday, July 22, 2009 4:10 PM, Galen Charlton [galen.charl...@liblime.com] wrote: Funny you should mention CVS. I have a general question for the MARC/Perl hackers: Ed mentioned a while back moving from CVS to a more modern VCS such as Subversion or (my preference) Git. I'm willing to do the legwork to get the repositories moved. Thoughts? Speaking as a hobbyist programmer, I've only used CVS, and would hope that a move to a different system wouldn't make it a more complicated or difficult to use system. Until last November, my main development machine was (and still would be) a PowerMac 7500/G3 with MacOS 9. When I tried to update SourceForge CVS this May using my Mac, I believe my SSH login failed (it had worked fine in August 2008), so I switched to updating SourceForge CVS using WinCvs on my Windows Vista laptop (Nov. 2008). I'm not sure what changed to prevent the Mac from being able to get a SSH connection to SourceForge, but I chalked it up to being an age thing (SourceForge update making old operating systems obsolete; or some change to SSH that I couldn't figure out how to fix in the MacSSH client; it does seem like it took a little bit of work getting WinCvs set up, as well), and that from now on, the Windows machine will be what I need to use to be able to update anything on SourceForge. So, as long as there is an easy-to-use Windows-based client for the other version control systems, then I probably wouldn't have a problem with switching. Thank you for your time, Bryan Baldus bryan.bal...@quality-books.com eij...@cpan.org http://home.inwave.com/eija
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
2008/10/29 Bill Erickson billserick...@gmail.com: Hi all, I ran across some gnarly MARC data today, which contained, among other things, MARC codes of . I realized that Marc::File::XML outputs the MARC tags, codes, and indicators without escaping them. This results, in my case, in invalid XML like: subfield code=France/subfield It seems reasonable that, regardless of the (horrible) content of the MARC, marc::file::xml should produce valid XML. Attached is a patch to explicitly escape the values before inserting them into the XML document under construction. I'm not sure if it's the best approach, but it got me up and running again. Thanks, Is anyone planning on applying this patch? It would be a shame to drop it on the floor. -- Dan Scott Laurentian University
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
2008/10/29 Bill Erickson [EMAIL PROTECTED]: Hi all, I ran across some gnarly MARC data today, which contained, among other things, MARC codes of . I realized that Marc::File::XML outputs the MARC tags, codes, and indicators without escaping them. This results, in my case, in invalid XML like: subfield code=France/subfield It seems reasonable that, regardless of the (horrible) content of the MARC, marc::file::xml should produce valid XML. Attached is a patch to explicitly escape the values before inserting them into the XML document under construction. I'm not sure if it's the best approach, but it got me up and running again. Any chance of including a sample (horrible) MARC record to include in a testcase? I'm not saying I would build a testcase for MARC::File::XML, but I might build one for File_MARC (PHP)... and a nice horrible MARC record from the wild would help. -- Dan Scott Laurentian University
Re: [Patch] Escape marc tag/code/indicators in Marc::File::XML
On Wed, Oct 29, 2008 at 5:01 PM, Dan Scott [EMAIL PROTECTED] wrote: 2008/10/29 Bill Erickson [EMAIL PROTECTED]: Hi all, I ran across some gnarly MARC data today, which contained, among other things, MARC codes of . I realized that Marc::File::XML outputs the MARC tags, codes, and indicators without escaping them. This results, in my case, in invalid XML like: subfield code=France/subfield It seems reasonable that, regardless of the (horrible) content of the MARC, marc::file::xml should produce valid XML. Attached is a patch to explicitly escape the values before inserting them into the XML document under construction. I'm not sure if it's the best approach, but it got me up and running again. Any chance of including a sample (horrible) MARC record to include in a testcase? I'm not saying I would build a testcase for MARC::File::XML, but I might build one for File_MARC (PHP)... and a nice horrible MARC record from the wild would help. Attached, including the post-escape XML version. -b ?xml version=1.0 encoding=UTF-8? record xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://www.loc.gov/MARC21/slim http://www.loc.gov/ standards/marcxml/schema/MARC21slim.xsd xmlns=http://www.loc.gov/MARC21/slim; leader00727nam 2200205 a 4500/leader controlfield tag=00103-0016458/controlfield controlfield tag=00519971103184734.0/controlfield controlfield tag=008970701s1997oru u000 0 eng u/controlfield datafield tag=035 ind1= ind2= subfield code=a(Sirsi) a351664/subfield /datafield datafield tag=050 ind1=0 ind2=0 subfield code=aML270.2/subfield subfield code=b.A6 1997/subfield /datafield datafield tag=100 ind1=1 ind2= subfield code=aAnthony, James R./subfield /datafield datafield tag=245 ind1=0 ind2=0 subfield code=aFrench baroque music from Beaujoyeulx to Rameau/subfield /datafield datafield tag=250 ind1= ind2= subfield code=aRev. and expanded ed./subfield /datafield datafield tag=260 ind1= ind2= subfield code=aPortland, OR :/subfield subfield code=bAmadeus Press,/subfield subfield code=c1997./subfield /datafield datafield tag=300 ind1= ind2= subfield code=a586 p. :/subfield subfield code=bmusic/subfield /datafield datafield tag=650 ind1= ind2=0 subfield code=aMusic/subfield subfield code=lt;France/subfield subfield code=y16th century/subfield subfield code=xHistory and criticism./subfield /datafield datafield tag=650 ind1= ind2=0 subfield code=aMusic/subfield subfield code=zFrance/subfield subfield code=y17th century/subfield subfield code=xHistory and criticism./subfield /datafield datafield tag=650 ind1= ind2=0 subfield code=aMusic/subfield subfield code=zFrance/subfield subfield code=y18th century/subfield subfield code=xHistory and criticism./subfield /datafield datafield tag=949 ind1= ind2= subfield code=aML 270.2 A6 1997/subfield subfield code=wLC/subfield subfield code=i30007006841505/subfield subfield code=rY/subfield subfield code=tBOOKS/subfield subfield code=lHUNT-CIRC/subfield subfield code=mHUNTINGTON/subfield /datafield datafield tag=596 ind1= ind2= subfield code=a1/subfield /datafield /record test.mrc Description: Binary data
