From rochkind at jhu.edu Mon Mar 7 14:58:37 2011 From: rochkind at jhu.edu (Jonathan Rochkind) Date: Mon, 07 Mar 2011 14:58:37 -0500 Subject: [Umlaut-general] move repo to github? Message-ID: <4D7538ED.9040108@jhu.edu> So I've been wanting to move the code repo to github, ever since I discovered how awesome git and github was. But was planning on waiting until I also had time to update Umlaut for Rails3 and a buncha other things, and just do it all at once. But rubyforge just changed something about their svn authentication, that I'm having trouble figuring out. You can't commit by entering your password anymore, you need to set up public key auth, but their documentation is kind of sparse and I can't figure out how to do it. So I might move to github sooner rather than later, if I can't figure out how to commit otherwise! Would have to change all the install docs to install by checkout out git/github instead of svn/rubyforge, kind of a pain. But any opinions pro or con? Scot, do you still have un-committed auth-related changes you'd like to commit, that will be harder to deal with if I move to github before you've committed them? (On the other hand, if you can figure out how to commit them to rubyforge, let me know!) From rochkind at jhu.edu Tue Mar 8 13:53:33 2011 From: rochkind at jhu.edu (Jonathan Rochkind) Date: Tue, 08 Mar 2011 13:53:33 -0500 Subject: [Umlaut-general] new HathiTrust service adapter Message-ID: <4D767B2D.2030703@jhu.edu> The existing HathiTrust service adapter is actually called MBooks, revealing it's anchient provenance before HathiTrust even was announced as such. It was based on API in the umich Mirlyn catalog that Bill Dueber awesomely provided, in part for Umlaut. I have committed a new service adapter, actually called HathiTrust, based on a different official HathiTrust API instead. I am deploying it in production myself today, hopefully there won't be any unexpected problems. If you are currently using the MBooks service, it would be a good idea to switch to the HathiTrust service instead. The old MBooks api that MBooks used is considered unsupported and legacy by bill dueber/umich, and could go away at any time. The HathiTrust adapter looks for full text or search inside in HathiTrust, based on matches to OCLCnumber, ISBN, or LCCN. The new one should possibly do a slightly better job of finding matches than the old one did, since the new HathiTrust API is better. The new one also does a better job of recognizing when a HathiTrust 'match' is just one volume of a multi-volume series, and not presenting that to the user as if its' full text for the whole thing. Instead, full text for possibly partial volumes is presented in the "Excerpts" section of the UI, and search-only for possibly partial volumes is just listed in the "See Also" (aka highlighted_links) section. Jonathan From scot.dalton at nyu.edu Mon Mar 21 09:23:38 2011 From: scot.dalton at nyu.edu (Scot Dalton) Date: Mon, 21 Mar 2011 09:23:38 -0400 Subject: [Umlaut-general] move repo to github? In-Reply-To: <4D7538ED.9040108@jhu.edu> References: <4D7538ED.9040108@jhu.edu> Message-ID: Hi Jonathan, Sorry for the delayed response. I was out on paternity leave. Just ran into the svn issue. Were you able to figure it out? If not, I'll start poking around, since I need to update the to the Hathi Trust service. I have some changes in the auth branch that need to be merged into trunk. If I can figure out the rubyforge svn issues, I'll try to merge those today. I haven't worked with git yet, so this will be a good opportunity to learn about it. What's your timeline for moving to github? Thanks, Scot On Mar 7, 2011, at Mar 7, 2:58 PM, Jonathan Rochkind wrote: > So I've been wanting to move the code repo to github, ever since I discovered how awesome git and github was. > > But was planning on waiting until I also had time to update Umlaut for Rails3 and a buncha other things, and just do it all at once. > > But rubyforge just changed something about their svn authentication, that I'm having trouble figuring out. You can't commit by entering your password anymore, you need to set up public key auth, but their documentation is kind of sparse and I can't figure out how to do it. > > So I might move to github sooner rather than later, if I can't figure out how to commit otherwise! Would have to change all the install docs to install by checkout out git/github instead of svn/rubyforge, kind of a pain. > > But any opinions pro or con? Scot, do you still have un-committed auth-related changes you'd like to commit, that will be harder to deal with if I move to github before you've committed them? (On the other hand, if you can figure out how to commit them to rubyforge, let me know!) > _______________________________________________ > Umlaut-general mailing list > Umlaut-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/umlaut-general -- Scot Dalton Phone: (212) 998-2674 Web Services Division of Libraries New York University From rochkind at jhu.edu Mon Mar 21 11:15:45 2011 From: rochkind at jhu.edu (Jonathan Rochkind) Date: Mon, 21 Mar 2011 11:15:45 -0400 Subject: [Umlaut-general] move repo to github? In-Reply-To: References: <4D7538ED.9040108@jhu.edu> Message-ID: <4D876BA1.6040203@jhu.edu> Yeah, I figured it out -- basically, you can't use username/password authentication on svn anymore, you need to use ssl cert public key authentication. For which there is kind of sort of documentation somewhere on rubyforge. I forget the precise steps I took to set it up, but if you can't figure it out I can try to retrace my steps. On 3/21/2011 9:23 AM, Scot Dalton wrote: > Hi Jonathan, > > Sorry for the delayed response. I was out on paternity leave. Just ran into the svn issue. Were you able to figure it out? If not, I'll start poking around, since I need to update the to the Hathi Trust service. > > I have some changes in the auth branch that need to be merged into trunk. If I can figure out the rubyforge svn issues, I'll try to merge those today. I haven't worked with git yet, so this will be a good opportunity to learn about it. What's your timeline for moving to github? > > Thanks, > Scot > > On Mar 7, 2011, at Mar 7, 2:58 PM, Jonathan Rochkind wrote: > >> So I've been wanting to move the code repo to github, ever since I discovered how awesome git and github was. >> >> But was planning on waiting until I also had time to update Umlaut for Rails3 and a buncha other things, and just do it all at once. >> >> But rubyforge just changed something about their svn authentication, that I'm having trouble figuring out. You can't commit by entering your password anymore, you need to set up public key auth, but their documentation is kind of sparse and I can't figure out how to do it. >> >> So I might move to github sooner rather than later, if I can't figure out how to commit otherwise! Would have to change all the install docs to install by checkout out git/github instead of svn/rubyforge, kind of a pain. >> >> But any opinions pro or con? Scot, do you still have un-committed auth-related changes you'd like to commit, that will be harder to deal with if I move to github before you've committed them? (On the other hand, if you can figure out how to commit them to rubyforge, let me know!) >> _______________________________________________ >> Umlaut-general mailing list >> Umlaut-general at rubyforge.org >> http://rubyforge.org/mailman/listinfo/umlaut-general > > -- > Scot Dalton > Phone: (212) 998-2674 > Web Services > Division of Libraries > New York University > > _______________________________________________ > Umlaut-general mailing list > Umlaut-general at rubyforge.org > http://rubyforge.org/mailman/listinfo/umlaut-general