<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
		<id>https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=128.220.8.101</id>
		<title>Code4Lib - User contributions [en]</title>
		<link rel="self" type="application/atom+xml" href="https://wiki.code4lib.org/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=128.220.8.101"/>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/Special:Contributions/128.220.8.101"/>
		<updated>2026-06-25T18:55:11Z</updated>
		<subtitle>User contributions</subtitle>
		<generator>MediaWiki 1.26.2</generator>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Code4Lib_Journal_Tech_Wishlist&amp;diff=7537</id>
		<title>Code4Lib Journal Tech Wishlist</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Code4Lib_Journal_Tech_Wishlist&amp;diff=7537"/>
				<updated>2011-02-14T16:43:10Z</updated>
		
		<summary type="html">&lt;p&gt;128.220.8.101: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Things on this page aren't neccesarily consensus, just things people listed as tech wishlist. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Seperate author names in individual fields in db, for better metadata generation.  (Then make export of DOAJ metadata use it, to make it a fully automated process!)&lt;br /&gt;
&lt;br /&gt;
* epub and/or PDF export of a complete issue&lt;br /&gt;
&lt;br /&gt;
* PDF of individual article&lt;br /&gt;
&lt;br /&gt;
* Include &amp;quot;cite as&amp;quot; text on each page, with several major citation formats filled in with our data. Especially important because we use an &amp;quot;article number&amp;quot;, rather than a page number -- which is supported by most citation formats, but it's not obvious from looking at an article what it's &amp;quot;article number&amp;quot; _is_, you have to know to get it from the URL. Makes it hard to cite correctly. &lt;br /&gt;
&lt;br /&gt;
* Automated list of &amp;quot;most viewed articles&amp;quot;, from WP statistics or Google Analytics?&lt;br /&gt;
&lt;br /&gt;
* Investigate usefulness for us: Here is a WordPress plugin designed to implement editorial workflows:&lt;br /&gt;
http://editflow.org/&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib Journal]]&lt;/div&gt;</summary>
		<author><name>128.220.8.101</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=6461</id>
		<title>How To Plan A Code4LibCon</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=How_To_Plan_A_Code4LibCon&amp;diff=6461"/>
				<updated>2010-12-06T17:24:07Z</updated>
		
		<summary type="html">&lt;p&gt;128.220.8.101: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;* Apply to be a host&lt;br /&gt;
&lt;br /&gt;
* Consider your action plan&lt;br /&gt;
** Identify your venues for both the conference and the hotel (if different). This is critical, as you'll want to get some cost estimates from each. When we hosted in Corvallis, the campus provided the conference space at a low cost, and this made running the conference much more affordable. When we hosted the conference in Portland, and held everything in a single hotel, we had to acquire 2x the amount of sponsorship than what appears to be normal.&lt;br /&gt;
** Speaking of sponsorship, I believe we average around 20k per year in sponsorships to help run the conference and keep the registration low. Factor this into your budget.&lt;br /&gt;
** Also, when you get cost estimates, don't forget to include food costs.&lt;br /&gt;
** WIRELESS: Always an issue it seems. If you are proposing to host the conference on a campus, check with your IT folks about any additional costs. If you are looking at a hotel or other venue, make sure you talk to them about bandwidth and costs. IMHO, the two things that really need to be addressed each year are connectivity and food - everything else generally manages itself in terms of facilities.&lt;br /&gt;
** See if your institution has a conference planning services group or something similar - if it does, then I highly recommend using them. They'll handle registration, budgeting, contracts, etc, and really make life easy.&lt;br /&gt;
** Regarding conference hotel, you'll want to make sure that there are blocks of rooms available - not usually too bad an issue in larger towns, but in some college or smaller towns, hotel rooms may be limited.&lt;br /&gt;
** Remember, your institution is taking the risk of covering any costs not covered by registrations and sponsorships. To this point, I believe the conference has always ended up in the black, but there is always a chance it won't in a given year. Drafting a rough budget before submitting a proposal is critical.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Get approved by the community&lt;br /&gt;
* Find a hotel, negotiate and sign a contract with them&lt;br /&gt;
* Invite the community to help with &lt;br /&gt;
* Have a timeline&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
== Important Public Resources ==&lt;br /&gt;
* Past calls for host sites: [http://code4lib.org/node/275 2010] - &lt;br /&gt;
* [http://dewey.library.nd.edu/mailing-lists/code4lib/ Code4Lib listserv]&lt;br /&gt;
* [http://groups.google.com/group/code4libcon Code4LibCon listserv]&lt;br /&gt;
* Sponsorship info (public)&lt;br /&gt;
* [http://code4lib.org/logo/ Logos]&lt;br /&gt;
&lt;br /&gt;
== Important Private Resources ==&lt;br /&gt;
* Code4LibCon-hostsite listserv&lt;br /&gt;
* Budgets from previous years&lt;br /&gt;
* Sponsorship info (private)&lt;br /&gt;
&lt;br /&gt;
== Shortly before the Conference ==&lt;br /&gt;
&lt;br /&gt;
=== Keynotes ===&lt;br /&gt;
# Contact speakers in advance to ask if they need anything, arrange airport pickup, etc&lt;br /&gt;
&lt;br /&gt;
=== Freenode IRC connection ===&lt;br /&gt;
Historically, conference attendees have had trouble maintaining persistent connections to the #code4lib IRC channel. We'd always assumed we were overwhelming the conference facility's Internet connection, but we were actually running into Freenode's IP-based connection limits. Freenode is supportive of the IRC-as-backchannel model, however, and they're happy to work with organizers to raise the connection limit.&lt;br /&gt;
&lt;br /&gt;
Contact the conference facility in advance and see if you can find out what your ''public IP address range'' will be during the conference. (If it starts with 10.*, 192.168.*, or 172.16.*, ask again -- those are &amp;quot;private&amp;quot; IP ranges used for connection sharing.)&lt;br /&gt;
&lt;br /&gt;
Once you have the IP address or range, send an email to [mailto:ilines@freenode.net ilines@freenode.net] containing a request to raise the connection limit. Include conference info, IP range(s), and the expected number of connections. For example:&lt;br /&gt;
&lt;br /&gt;
 To: ilines@freenode.net&lt;br /&gt;
 &lt;br /&gt;
 Hello,&lt;br /&gt;
 &lt;br /&gt;
 I'm helping plan the code4lib 2010 conference, taking place in Asheville, NC next week. &lt;br /&gt;
 Since our backchannel runs through #code4lib on Freenode, we're trying to plan ahead &lt;br /&gt;
 to avoid running up against the connection limit. Would it be possible to raise the cap &lt;br /&gt;
 for us during the conference? Details follow.&lt;br /&gt;
 &lt;br /&gt;
 Conference: code4lib 2010 &amp;lt; http://code4lib.org/conference/2010/ &amp;gt;&lt;br /&gt;
 Dates: February 22-26, 2010&lt;br /&gt;
 Attendees: 250&lt;br /&gt;
 Location: Renaissance Asheville Hotel, Asheville, NC&lt;br /&gt;
 IP Ranges: 12.21.216.106 and the entire 12.21.217.0/24 block&lt;br /&gt;
 &lt;br /&gt;
 We encourage in-channel participation, so we expect a high percentage of attendees to &lt;br /&gt;
 be connected at once. We'll also have two or three channel bots connected from the &lt;br /&gt;
 conference for the lobby monitors.&lt;br /&gt;
 &lt;br /&gt;
 Please let me know if you need any further information, and thanks very much for &lt;br /&gt;
 your help!&lt;br /&gt;
 &lt;br /&gt;
 Michael&lt;br /&gt;
&lt;br /&gt;
I received an automated reply with a ticket number almost instantly, but didn't hear back after that. I sent a quick followup early on the morning of the 22nd, and received a response (from a human) letting me know that it had been taken care of.&lt;br /&gt;
&lt;br /&gt;
Additional support is available from the helpful volunteer Freenode staff in the #freenode channel.&lt;br /&gt;
&lt;br /&gt;
== At the Conference ==&lt;br /&gt;
&lt;br /&gt;
===Keynotes===&lt;br /&gt;
# Water at the podium&lt;br /&gt;
# Speaker gifts&lt;br /&gt;
# Dinner plans&lt;br /&gt;
&lt;br /&gt;
=== Timers ===&lt;br /&gt;
* Sit in the front of the room&lt;br /&gt;
* Have several people&lt;br /&gt;
* You may want to use an extra machine&lt;br /&gt;
* Here's what some of the software looks like: http://www.flickr.com/photos/schwartzray/4393891356/ (ask Ed Corrado for details)&lt;br /&gt;
* Dan Chudnov says the best free timer app for OSX is http://www.apimac.com/timer/&lt;br /&gt;
&lt;br /&gt;
=== Lightning Talks ===&lt;br /&gt;
* Everybody lines up ahead of time (image: http://www.flickr.com/photos/schwartzray/4393881044/ )&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
=== Ask Anything===&lt;br /&gt;
* Need mics for people to line up at (image: http://www.flickr.com/photos/schwartzray/4393838640/ )&lt;br /&gt;
&lt;br /&gt;
===Book Raffle===&lt;br /&gt;
* (image: http://www.flickr.com/photos/schwartzray/4393619144/ with people for context: http://www.flickr.com/photos/schwartzray/4393623802/ and http://www.flickr.com/photos/schwartzray/4384550127/ ), better if there's a table&lt;br /&gt;
&lt;br /&gt;
=== Flipcharts ===&lt;br /&gt;
Flipcharts can be useful, but it's important to decide what to put on the wiki/website and what to put on a flipchart:&lt;br /&gt;
images: http://www.flickr.com/photos/schwartzray/4392998501/ http://www.flickr.com/photos/47860563@N05/4388430079/&lt;br /&gt;
&lt;br /&gt;
== Suggested Timeline ==&lt;br /&gt;
* See [[C4L2010planning]] for an example &lt;br /&gt;
&lt;br /&gt;
[[Category: Code4Lib2010]]&lt;br /&gt;
[[Category: Code4Lib2011]]&lt;/div&gt;</summary>
		<author><name>128.220.8.101</name></author>	</entry>

	<entry>
		<id>https://wiki.code4lib.org/index.php?title=Umlaut_wishlist&amp;diff=6410</id>
		<title>Umlaut wishlist</title>
		<link rel="alternate" type="text/html" href="https://wiki.code4lib.org/index.php?title=Umlaut_wishlist&amp;diff=6410"/>
				<updated>2010-11-22T17:07:35Z</updated>
		
		<summary type="html">&lt;p&gt;128.220.8.101: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[Category:Umlaut]]&lt;br /&gt;
&lt;br /&gt;
Some actual current future plans:&lt;br /&gt;
&lt;br /&gt;
* Fix HathiTrust adapter to use new HT plugin, including not showing fulltext for just portions of a serial. (Or showing it in 'see also' section only)&lt;br /&gt;
&lt;br /&gt;
* Use OCLC xISBN to find HT and Internet Archive/OCA matches?&lt;br /&gt;
&lt;br /&gt;
* Rails3&lt;br /&gt;
&lt;br /&gt;
* Internet Archive -- use new OL/IA api, discover search-inside-the-book. &lt;br /&gt;
&lt;br /&gt;
* WorldCat, use new api, link directly to nearest public library in 'see also' or elsewhere. &lt;br /&gt;
&lt;br /&gt;
* CiteSeerX -- source of 'cited by' info, AND, most excitingly, open access pre-prints. But their Atom/RSS feeds (the only API I could find) don't seem to advertise enough info to actually use these features. Would need to talk to developer team -- possibly offer to help code? Also not entirely clear how big their corpus actually is, if it's worth it. &lt;br /&gt;
&lt;br /&gt;
* Try screen-scraping Google Scholar (and maybe Microsoft Academic) to get the open access full text links they find. &lt;br /&gt;
&lt;br /&gt;
* When no full text is found, provide link to search on Google Scholar, or Bing Academic?  Need to have sufficient metadata to create the search. Oct 2010 Library Technolgoy Reports article has some ideas, I think. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
'''old''' Desired or planned features. &lt;br /&gt;
&lt;br /&gt;
* Check for similar articles from: http://biosemantics.org/jane/faq.php#api&lt;br /&gt;
&lt;br /&gt;
* Full-text availability check from http://chroniclingamerica.loc.gov/ -- check by title/city, check by lccn (?), able to check particular dates/link to particular dates and/or pages of paper?&lt;br /&gt;
&lt;br /&gt;
* Allow a service_response to have a tree relationship to children, so for instance alternate versions of a text can be attached as children of the main link, expandable by the user. &lt;br /&gt;
&lt;br /&gt;
* http://export.arxiv.org/api_help/   !!!!&lt;br /&gt;
&lt;br /&gt;
* PubMed Central full text lookup http://www.ncbi.nlm.nih.gov/entrez/query/static/esearch_help.html (SFX may already do this?)&lt;br /&gt;
&lt;br /&gt;
* Journal ToC from CiteULike&lt;br /&gt;
&lt;br /&gt;
* Parsing of formatted references from an entry screen. Use http://wing.comp.nus.edu.sg/parsCit/ package. Very interesting!  Or a similar UCOP package: http://purl.net/net/egh/hmm-citation-extractor/ See list of such packages here under &amp;quot;Other Parsing Tools&amp;quot; http://freecite.library.brown.edu/&lt;br /&gt;
&lt;br /&gt;
* LibraryThing open knowledge API for more data. http://www.librarything.com/blog/2008/08/free-web-services-api-to-common.php&lt;br /&gt;
&lt;br /&gt;
* Connect to internet linked movie database on movies: http://www.linkedmdb.org/&lt;br /&gt;
&lt;br /&gt;
* Add information about the conversation happening around an article with Scintilla if we have a URL, PMID or DOI (Alf at Scintilla would prefer us NOT to use the API for high-traffic. But we can copy his techniques internally to Umlaut. CrossRef and PubMed for &amp;quot;cited by&amp;quot; on DOI and PMID identifiers are a good idea. He has also reverse engineered the Scopus javascript api to allow server-side json access. http://hublog.hubmed.org/archives/001512.html):&lt;br /&gt;
     http://hublog.hubmed.org/archives/001609.html&lt;br /&gt;
     Unofficially it will return json:&lt;br /&gt;
     http://scintilla.nature.com/conversations?uri=info%3Adoi%2F10.1371%2Fjournal.pmed.0020124&amp;amp;format=json&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Rochester “Getting Users Fulltext” style code to skip right to the full text, skipping content-provider metadata pages.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* UMich Mirlyn for metadata enrichment? &lt;br /&gt;
     http://webservices.itcs.umich.edu/mediawiki/MLibraryAPI/index.php/Mirlynapi:Home&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* xISBN/thingISBN use. (Some thought is required in how to integrate this while avoiding false positives). Bowker ISSN service for metadata enhancement. OCLC xISSN?  Integrate preceding/succeeding title information from OPAC or xISSN?&lt;br /&gt;
&lt;br /&gt;
* LibraryLookup: http://xisbn.worldcat.org/liblook/index.htm  At least until xISBN is baked in we could provide a link to this service. Increases the chances of finding a desired book in the catalog through work set grouping. Used by LibX.&lt;br /&gt;
      http://xisbn.worldcat.org/liblook/resolve.htm?res_id=http://www.iucat.iu.edu&amp;amp;rft.isbn=0451530942&amp;amp;url_ver=Z39.88-2004&amp;amp;rft_val_fmt=info:ofi/fmt:kev:mtx:book&lt;br /&gt;
&lt;br /&gt;
* Journal covers from Ulrich's via screen-scraping (or Ulrich's/sersol built in api?)&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Connotea integration&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Fetch ToC from LC. Screen scrape, I guess? Or z3950? Any other content from LC?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Link to Books In Print ala Notre Dame. &lt;br /&gt;
http://www.library.nd.edu/eresources/findit/findit.cgi?doc_num=001939269&amp;amp;aleph_session=U5AVHRXD5QB1CGDFDSVJ9DSY2UA6QNCGVEU8EYRX9NNMIQ429Q-54668%22&lt;br /&gt;
example &lt;br /&gt;
&lt;br /&gt;
* bip search url? :&lt;br /&gt;
http://www.booksinprint.com/merge_shared/Search/advsearch.asp%3FdateState%3DY%26txtAction%3D%26BooleanSearch%3D%26SType%3Dadv%26collection%3DBIP%26QueryMode%3DSimple%26ResultCount%3D25%26ResultTemplate%3Dmbbookresult_fl.hts%26navPage%3D1%26SrchFrm%3DAdv%26ScoreThreshold%3D0%26Criteria1%3DISBN%26CriteriaText1%3D0838935370&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* SFX plugin:  Notice when first title given is non-roman, and look for roman title to enhance metadata with when so. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* HIP and other OPAC searchers should pull ToC from MARC 505 when present.  And 856's judged to be ToC in ToC, not full text. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Fix Umlaut Referent to more easily allow multiple authors. Architectural change neccessary to get a lot of this stuff working right. &lt;br /&gt;
&lt;br /&gt;
* &amp;quot;Cited by&amp;quot; service. Scopus via screen scraping? (scopus javascript api? http://www.scopus.com/scsearchapi/ See also http://hublog.hubmed.org/archives/001512.html ) ISI Web of Science is too hard to even screen scrape the interface is such a mess, but Scopus looks do-able.  Google scholar?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Enhance metadata to have full metadata for a refworks etc export. Using: CrossRef?  Metalib?  Anything else?&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* A general purpose responsecache. Schema: Date, service/source, key.  Use for caching image urls, ToC urls from LC, etc. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Fix Worldcat registry auto-discovery. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Add a Worldcat search that uses API, instead of screen scrape. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Switch OCA search to use OCA native APIs, instead of indexdata mirror index. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* fix unapi in umlaut. unapi to rsi?  For zotero. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Change background to use Spawn plugin instead of manual threading. Investigating using spawn with fork instead of thread (terry reese on limited pool of forks). &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Crazy idea for an abstract interface/architecture to support querying web service apis that require client side javascript, like Google Books and Scopus. &lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* Integrate my various local document delivery services into menu of options when full text isn’t available. More generally, a clear architecture for providing localized doc delivery services in addition to a single ILL link.&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
* SFX adaptor: Add a &amp;quot;rollup&amp;quot; feature that pays attention to dates to avoid eliminating coverage.&lt;/div&gt;</summary>
		<author><name>128.220.8.101</name></author>	</entry>

	</feed>