Code4Lib - User contributions [en]

Code4Lib Montreal meeting notes 20181023

2018-10-25T13:02:40Z

Dbs: Correct a name

= Code4Lib Montreal 2018-10-23 =

== Attendees ==

* Chris Trudeau - recent McGill SIS graduate
* Martin ?? - Health Sciences liaison, McGill
* Stephana Bretweiser - CCA
* Tim Walsh - Digital Preservation librarian, Concordia
* John ?? - Digital Archivist, Concordia
* Clara Turp - Metadata Analyst Librarian, McGill
* Jessica Reeve - Senior Electronic Resources
* Tomasz Langenbauer - Digital Projects, Concordia
* Rebecca Nicholson - Web group, McGill
* Eka Grguric - Web Librarian, McGill
* Dan Scott - Systems librarian, Laurentian / McGill student

== Mandat du groupe et description / Group's description and mandate ==

Brief discussion about what the mandate of the group should be:

* Learning about technology and coding through doing; workshops
* Building a community - across universities, colleges, public institutions in Montreal
* Informal

We like https://code4lib.org/about

* '''Action''' Clara will customize the Code4Lib statement, ensuring it reflects a Montreal & bilingual context

== Presentations ==

Sarah Severson: sick, will present conference report from DLF next time

=== Chris Trudeau: citations to reserves ===

Idea: instead of faculty emailing the library with their individual requests for items that need to be placed on reserve, why not extract the citations from the course outline / syllabus (in PDF or Word format) and automatically generate reserve requests?

==== Feedback ====

* McGill used to have faculty upload syllabi, but eventually stopped because of resistance ("private information")
* McGill accepts reserve requests in any format: email, in person, paper
* Tomasz built something like this for Concordia in 2009 and is willing to share it; but faculty wanted the ability to submit the entire syllabus; or paste in a full citation; or fill out the parts field-by-field

=== Tim Walsh, Bulk Reviewer ===

This is a project Tim started working on while a Harvard Fellow over the summer; the idea is to use forensics tools for the power of archives. Requires identifying individual files accurately rather than the broader-based "yeah it looks like there are credit card numbers on this hard drive" approach that forensics are interested in.

* Identifies, reviews, and removes sensitive files in disk images and directories, regardless of file format
* Sensitive info - SSN, credit card numbers, phone numbers, email addresses, internet history, EXIF metadata, GPS data, custom search terms, Windows registry (program install history)
* Built using Django, Vue.js, bulk_extractor, DFXML, and Docker
* bulk_extractor generates text files or a SQLite database that normally gets processed into a histogram; this processes the data to instead support a Web browser front end and identify the individual files that may be problematic

==== Problems ====

* Many false positives (e.g. all 9 digit numbers are identified as SSNs); Tim isn't sure any of these tools have a high level of confidence
* Tooling is all American-based, so adding something like a SIN requires C++ (Tomasz is willing to help!)

== Next meeting ==

* November - Sarah and John to present
* Mid-December - social

Code4Lib Montreal

2018-10-25T00:34:02Z

Dbs: Oh yeah, Mediawiki hates 2018-10-23 formatted links...

Welcome to the page of the new Code4Lib local group in Montreal.

[[Code4Lib Montreal Fr|Click here for the French Page | Cliquez ici pour la page en français]]

=== General information ===

Email [mailto:clara.turp@mcgill.ca Clara Turp] for more information.

Subscribe to our mailing list: http://www.listes.umontreal.ca/wws/info/code4lib-mtl to learn about new events and our next meetings.<br>

Slack Channel and Hashtag: #code4lib-mtl <br>
To add the channel, you must join the general code4lib slack. [https://groups.google.com/forum/#!topic/code4libcon/0q8i4yTI7y8 Click here to join the Code4Lib slack.] <br>
Plan of things we want to learn and do: [https://docs.google.com/spreadsheets/d/1OPMCNoWa7b5VJpn7Zg80rsKr8A9rhGoUMQoxMOjIC7o/edit Vote and add to the plan]

=== Next Meetup ===

September 21, 2018 at 5:15 pm - 5a7 social get together extravaganza. Location: Brutopia, 1219 Crescent St.<br>
October 23, 2018 at 4:00 pm - Lightning talks. Location: LB-205, Webster Library, 1400 Maisonneuve <br>

=== Past Meetups and meeting notes ===

* October 23, 2018 - Lightning talks [[Code4Lib Montreal meeting notes 20181023|meeting notes]]
* August 21, 2018 Planning session: [https://docs.google.com/document/d/1xHJOhwPL_jl-tp2X5JTfRauMAW6BKDry4rytYVj7GTY/edit#heading=h.cyxn5hqwzw5b Meeting notes]
* June 20, 2018 Code4Lib Montreal kick-off meeting: [https://docs.google.com/document/d/1vLuBjB8ivQa-xBYP1p-JEPw1VjJOK1E_b_WbF7FtApk/edit Meeting notes]

Code4Lib Montreal meeting notes 20181023

2018-10-25T00:33:14Z

Dbs: Formatting for Tim's presentation

= Code4Lib Montreal 2018-10-23 =

== Attendees ==

* Chris Trudeau - recent McGill SIS graduate
* Martin ?? - Health Sciences liaison, McGill
* Stephana Bretweiser - CCA
* Tim Walsh - Digital Preservation librarian, Concordia
* John ?? - Digital Archivist, Concordia
* Clara Turp - Metadata Analyst Librarian, McGill
* Jessica Reeve - Senior Electronic Resources
* Tomasz Langenbauer - Digital Projects, Concordia
* Rebecca Nicholson - Web group, McGill
* Eka Grigorik - Web Librarian, McGill
* Dan Scott - Systems librarian, Laurentian / McGill student

== Mandat du groupe et description / Group's description and mandate ==

Brief discussion about what the mandate of the group should be:

* Learning about technology and coding through doing; workshops
* Building a community - across universities, colleges, public institutions in Montreal
* Informal

We like https://code4lib.org/about

* '''Action''' Clara will customize the Code4Lib statement, ensuring it reflects a Montreal & bilingual context

== Presentations ==

Sarah Severson: sick, will present conference report from DLF next time

=== Chris Trudeau: citations to reserves ===

Idea: instead of faculty emailing the library with their individual requests for items that need to be placed on reserve, why not extract the citations from the course outline / syllabus (in PDF or Word format) and automatically generate reserve requests?

==== Feedback ====

* McGill used to have faculty upload syllabi, but eventually stopped because of resistance ("private information")
* McGill accepts reserve requests in any format: email, in person, paper
* Tomasz built something like this for Concordia in 2009 and is willing to share it; but faculty wanted the ability to submit the entire syllabus; or paste in a full citation; or fill out the parts field-by-field

=== Tim Walsh, Bulk Reviewer ===

This is a project Tim started working on while a Harvard Fellow over the summer; the idea is to use forensics tools for the power of archives. Requires identifying individual files accurately rather than the broader-based "yeah it looks like there are credit card numbers on this hard drive" approach that forensics are interested in.

* Identifies, reviews, and removes sensitive files in disk images and directories, regardless of file format
* Sensitive info - SSN, credit card numbers, phone numbers, email addresses, internet history, EXIF metadata, GPS data, custom search terms, Windows registry (program install history)
* Built using Django, Vue.js, bulk_extractor, DFXML, and Docker
* bulk_extractor generates text files or a SQLite database that normally gets processed into a histogram; this processes the data to instead support a Web browser front end and identify the individual files that may be problematic

==== Problems ====

* Many false positives (e.g. all 9 digit numbers are identified as SSNs); Tim isn't sure any of these tools have a high level of confidence
* Tooling is all American-based, so adding something like a SIN requires C++ (Tomasz is willing to help!)

== Next meeting ==

* November - Sarah and John to present
* Mid-December - social

Code4Lib Montreal meeting notes 20181023

2018-10-25T00:30:49Z

Dbs: First stab at notes

= Code4Lib Montreal 2018-10-23 =

== Attendees ==

* Chris Trudeau - recent McGill SIS graduate
* Martin ?? - Health Sciences liaison, McGill
* Stephana Bretweiser - CCA
* Tim Walsh - Digital Preservation librarian, Concordia
* John ?? - Digital Archivist, Concordia
* Clara Turp - Metadata Analyst Librarian, McGill
* Jessica Reeve - Senior Electronic Resources
* Tomasz Langenbauer - Digital Projects, Concordia
* Rebecca Nicholson - Web group, McGill
* Eka Grigorik - Web Librarian, McGill
* Dan Scott - Systems librarian, Laurentian / McGill student

== Mandat du groupe et description / Group's description and mandate ==

Brief discussion about what the mandate of the group should be:

* Learning about technology and coding through doing; workshops
* Building a community - across universities, colleges, public institutions in Montreal
* Informal

We like https://code4lib.org/about

* '''Action''' Clara will customize the Code4Lib statement, ensuring it reflects a Montreal & bilingual context

== Presentations ==

Sarah Severson: sick, will present conference report from DLF next time

=== Chris Trudeau: citations to reserves ===

Idea: instead of faculty emailing the library with their individual requests for items that need to be placed on reserve, why not extract the citations from the course outline / syllabus (in PDF or Word format) and automatically generate reserve requests?

==== Feedback ====

* McGill used to have faculty upload syllabi, but eventually stopped because of resistance ("private information")
* McGill accepts reserve requests in any format: email, in person, paper
* Tomasz built something like this for Concordia in 2009 and is willing to share it; but faculty wanted the ability to submit the entire syllabus; or paste in a full citation; or fill out the parts field-by-field

=== Tim Walsh, Bulk Reviewer ===
Identifies, reviews, and removes sensitive files in disk images and directories, regardless of file format
Sensitive info - SSN, credit card numbers, phone numbers, email addresses, internet history, EXIF metadata, GPS data, custom search terms, Windows registry (program install history)
Built using Django, Vue.js, bulk_extractor, DFXML, and Docker
bulk_extractor generates text files or a SQLite database that normally gets processed into a histogram; this processes the data to instead support a Web browser front end and identify the individual files that may be problematic
Problems:
Many false positives (e.g. all 9 digit numbers are identified as SSNs); Tim isn't sure any of these tools have a high level of confidence
Tooling is all American-based, so adding something like a SIN requires C++ (Tomasz is willing to help!)

== Next meeting ==

* November - Sarah and John to present
* Mid-December - social

Code4Lib Montreal

2018-10-25T00:22:41Z

Dbs: Better link formatting

Welcome to the page of the new Code4Lib local group in Montreal.

[[Code4Lib Montreal Fr|Click here for the French Page | Cliquez ici pour la page en français]]

=== General information ===

Email [mailto:clara.turp@mcgill.ca Clara Turp] for more information.

Subscribe to our mailing list: http://www.listes.umontreal.ca/wws/info/code4lib-mtl to learn about new events and our next meetings.<br>

Slack Channel and Hashtag: #code4lib-mtl <br>
To add the channel, you must join the general code4lib slack. [https://groups.google.com/forum/#!topic/code4libcon/0q8i4yTI7y8 Click here to join the Code4Lib slack.] <br>
Plan of things we want to learn and do: [https://docs.google.com/spreadsheets/d/1OPMCNoWa7b5VJpn7Zg80rsKr8A9rhGoUMQoxMOjIC7o/edit Vote and add to the plan]

=== Next Meetup ===

September 21, 2018 at 5:15 pm - 5a7 social get together extravaganza. Location: Brutopia, 1219 Crescent St.<br>
October 23, 2018 at 4:00 pm - Lightning talks. Location: LB-205, Webster Library, 1400 Maisonneuve <br>

=== Past Meetups and meeting notes ===

* October 23, 2018 - Lightning talks [[Code4Lib Montreal meeting notes 2018-10-23|meeting notes]]
* August 21, 2018 Planning session: [https://docs.google.com/document/d/1xHJOhwPL_jl-tp2X5JTfRauMAW6BKDry4rytYVj7GTY/edit#heading=h.cyxn5hqwzw5b Meeting notes]
* June 20, 2018 Code4Lib Montreal kick-off meeting: [https://docs.google.com/document/d/1vLuBjB8ivQa-xBYP1p-JEPw1VjJOK1E_b_WbF7FtApk/edit Meeting notes]

Code4Lib Montreal

2018-10-25T00:22:13Z

Dbs: Meeting notes for October 23rd

Welcome to the page of the new Code4Lib local group in Montreal.

[[Code4Lib Montreal Fr|Click here for the French Page | Cliquez ici pour la page en français]]

=== General information ===

Email [mailto:clara.turp@mcgill.ca Clara Turp] for more information.

Subscribe to our mailing list: http://www.listes.umontreal.ca/wws/info/code4lib-mtl to learn about new events and our next meetings.<br>

Slack Channel and Hashtag: #code4lib-mtl <br>
To add the channel, you must join the general code4lib slack. [https://groups.google.com/forum/#!topic/code4libcon/0q8i4yTI7y8 Click here to join the Code4Lib slack.] <br>
Plan of things we want to learn and do: [https://docs.google.com/spreadsheets/d/1OPMCNoWa7b5VJpn7Zg80rsKr8A9rhGoUMQoxMOjIC7o/edit Vote and add to the plan]

=== Next Meetup ===

September 21, 2018 at 5:15 pm - 5a7 social get together extravaganza. Location: Brutopia, 1219 Crescent St.<br>
October 23, 2018 at 4:00 pm - Lightning talks. Location: LB-205, Webster Library, 1400 Maisonneuve <br>

=== Past Meetups and meeting notes ===

* October 23, 2018 - Lightning talks [[Code4Lib Montreal meeting notes 2018-10-23]]
* August 21, 2018 Planning session: [https://docs.google.com/document/d/1xHJOhwPL_jl-tp2X5JTfRauMAW6BKDry4rytYVj7GTY/edit#heading=h.cyxn5hqwzw5b Meeting notes]
* June 20, 2018 Code4Lib Montreal kick-off meeting: [https://docs.google.com/document/d/1vLuBjB8ivQa-xBYP1p-JEPw1VjJOK1E_b_WbF7FtApk/edit Meeting notes]

Code4Lib Journal WordPress Input Guidelines

2018-04-26T17:12:00Z

Dbs: Typo

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Tom Keays).

==Proofs for Authors==
A read-only login that is shared with authors can be found in the 'Administrivia' tab/worksheet of our Google Docs article tracking spreadsheet.

==Title==
Title, including the subtitle, goes in the "Title" field.

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

==Article Content==
The body of the article goes in the "Post" field. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Headings===
The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article,
<code><h3></code> for sub-sections, <code><h4></code> if you need a lower level. <code><h2></code> are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. <code><h3></code> and <code><h4></code> are in "Sentence case" -- only the first word is capitalized. Any header from second- to sixth-level may be used as appropriate.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html.
Fortunately, WP has a built-in feature to help with this.
Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon.
This transforms Word's html into really nice pretty html.
Alternatively, use the [http://www.textfixer.com/html/convert-word-to-html.php Word DOC to HTML converter].

===Figures & Tables===
Figures and tables are centered, placed inside a P or DIV with class of "caption". In general, we bold the figure / table label using the strong tag.

For example:
<pre>
<p class = "caption">
<img src = "....">
<strong>Figure X.</strong> How to Caption an Image.
</p>

<div class = "caption">
<strong>Table X.</strong> How to Caption a Table.
<table>
<tr>...</tr>
</table>
</div>
</pre>
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.

===Images and Attached Content===
In-line images should be no wider than 500px. See above section for captioning and image

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to login.ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. This sort of url will be used in the "<img src>" tag:
/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask Tom Keays for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

==== Video ====

We haven't had too much video, but we just had one (a screencast). The option we used was hosting on archive.org. Upload the video, click on the IA 'pillars' icon on the resulting video on the archive.org page to get an 'iframe' embed code, which works fine in our wordpress html source, and I believe the archive.org infrastructure will take care of translating the video to multiple formats and delivering in the proper format for a given browser. Very convenient.

Include a visible link to the archive.org URL for the individual video page as a caption, so printed or otherwise captured versions of the article will always have that link.

You don't need to use archive.org if you or we figure out a better way, it's just one option that worked very conveniently so far.

===Code===

If code is attached as a file, follow the directions above for attached images, except:

* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extension, so if you an "s" on the end of .php files, it does syntax highlighting for you, e.g.:
<filename>.phps

Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:

<pre>
[sourcecode language='php']
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed
[/sourcecode]
</pre>

If the language parameter is not set, it will default to "text" (no syntax highlighting). Supported languages include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>. For a full list consult: http://en.support.wordpress.com/code/posting-source-code/

Note: do not surround code with <tt><pre></tt> tags, as the <tt>[sourcecode]</tt> tag itself will generate the necessary HTML.

For more subtleties of code formatting, see this gist from editor Péter Király https://gist.github.com/pkiraly/c48193925ad3806c31ef010b58e8600f

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

Abstracts should be placed in the Excerpt box, displayed a little ways below the "Post" field. If you do not see the Excerpt box, look under "Screen Options" in the top right of the page. Selecting the down arrow will display fields to show on the screen. Make sure that 'Excerpt' is selected. This will display the Excerpt (abstract) input box on the page.

Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.

It appears the COinS generator at http://generator.ocoins.info/ is no longer in service. An alternative is [https://www.zotero.org/download/ Zotero's stand alone citation software].
After creating a citation, simply right click the citation and choose export / format: coins.
* Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it. For an example see the [http://journal.code4lib.org/articles/7922 References section of a published article including coins].

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. Italicize the author's name when it is first used (for example, "''Foo Bar'' is a librarian at..."). We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncategorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Submit URLS to Internet Archives for harvest ([https://gist.github.com/ruthtillman/fa7562989f299e4904c7fb0448d1fc83#file-waybacksubmit-py Wayback Submission Script] )
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
# Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2015-04-06T14:00:16Z

Dbs: Italicize the author's name in the "About the author(s)" section

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Tom Keays).

==Proofs for Authors==
A read-only login that is shared with authors can be found in the 'Administrivia' tab/worksheet of our Google Docs article tracking spreadsheet.

==Title==
Title, including the subtitle, goes in the "Title" field.

Article titles are in Title Case -- all major words capitalized. The title is followed by an abstract, which will be pulled from the excerpt section lower on the post page, and byline of the form "by Author" or "by Author 1, Author 2, and Author 3".

==Article Content==
The body of the article goes in the "Post" field. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Headings===
The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article,
<code><h3></code> for sub-sections, <code><h4></code> if you need a lower level. <code><h2></code> are in "Title Case" -- all words capitalized, short words (the, a, in, up, over, about) should not be. <code><h3></code> and <code><h4></code> are in "Sentence case" -- only the first word is capitalized. Any header from second- to sixth-level may be used as appropriate.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html.
Fortunately, WP has a built-in feature to help with this.
Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon.
This transforms Word's html into really nice pretty html.
Alternatively, use the [http://www.textfixer.com/html/convert-word-to-html.php Word DOC to HTML converter].

===Figures & Tables===
Figures and tables are centered, placed inside a P or DIV with class of "caption". In general, we bold the figure / table label using the strong tag.

For example:
<pre>
<p class = "caption">
<img src = "....">
<strong>Figure X.</strong> How to Caption an Image.
</p>

<div class = "caption">
<strong>Table X.</strong> How to Caption a Table.
<table>
<tr>...</tr>
</table>
</div>
</pre>
Captions for figures appear beneath the figure, centered, with "Figure X:" in bold, the descriptive text in sentence case, plain text.

Captions for tables and code appear above the table, centered, with "Table X:" in bold, the descriptive text in sentence case, plain text.

===Images and Attached Content===
In-line images should be no wider than 500px. See above section for captioning and image

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to login.ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask Tom Keays for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

==== Video ====

We haven't had too much video, but we just had one (a screencast). The option we used was hosting on archive.org. Upload the video, click on the IA 'pillars' icon on the resulting video on the archive.org page to get an 'iframe' embed code, which works fine in our wordpress html source, and I believe the archive.org infrastructure will take care of translating the video to multiple formats and delivering in the proper format for a given browser. Very convenient.

Include a visible link to the archive.org URL for the individual video page as a caption, so printed or otherwise captured versions of the article will always have that link.

You don't need to use archive.org if you or we figure out a better way, it's just one option that worked very conveniently so far.

===Code===

If code is attached as a file, follow the directions above for attached images, except:

* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, it does syntax highlighting for you, e.g.:
<filename>.phps

Code samples entered as preformatted text, as in the following example, are automagically color highlighted in Wordpress by the [http://wordpress.org/extend/plugins/syntaxhighlighter/ SyntaxHighlighter] plugin:

<pre>
[sourcecode language='php']
RAW HTML/PHP/XML/Etc. code goes here; change language (in above line) as needed
[/sourcecode]
</pre>

If the language parameter is not set, it will default to "text" (no syntax highlighting). Supported languages include <tt>cpp, c, c++, c#, c-sharp, csharp, css, delphi, java, js, jscript, javascript, pascal, php, py, python, rb, ruby, rails, ror, sql, vb, vb.net, xml, html, xhtml, and xslt</tt>. Pretty much everything except <tt>perl</tt>. For a full list consult: http://en.support.wordpress.com/code/posting-source-code/

Note: do not surround code with <tt><pre></tt> tags, as the <tt>[sourcecode]</tt> tag itself will generate the necessary HTML.

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

Abstracts should be placed in the Excerpt box, displayed a little ways below the "Post" field. If you do not see the Excerpt box, look under "Screen Options" in the top right of the page. Selecting the down arrow will display fields to show on the screen. Make sure that 'Excerpt' is selected. This will display the Excerpt (abstract) input box on the page.

Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.

It appears the COinS generator at http://generator.ocoins.info/ is no longer in service. An alternative is [https://www.zotero.org/download/ Zotero's stand alone citation software].
After creating a citation, simply right click the citation and choose export / format: coins.
* Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it. For an example see the [http://journal.code4lib.org/articles/7922 References section of a published article including coins].

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. Italicize the author's name when it is first used (for example, "''Foo Bar'' is a librarian at..."). We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
# Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Customizations

2014-08-24T02:29:03Z

Dbs: Fix typo (Akimset)

==Plugins==

===Anti-Spam===
;[http://akismet.com/ Akismet]
:Filters out spam-link comments based on their content
;[http://wordpress.org/plugins/wp-recaptcha/ WP-reCAPTCHA]
:Requires users to copy a distorted word before they can comment. We disabled this plugin at one point due to accessibility issues. However, we suffered a spam storm in May 2014 that required either disabling comments on all posts (not trivial) or reinstalling the CAPTCHA plugin.

===Metadata===
;DOAJ Export
:Provides information about your posts formatted according to the DOAJ Article XML Schema. (J. Brinley)
;[http://www.lackoftalent.org/michael/blog/unapi-wordpress-plug-in/ unAPI Server]
:Provides information about articles. Useful for Zotero users. (M. Giarlo)
;[http://www.wallandbinkley.com/quaedam/ COinS Quicktags Button] - no longer installed; buggy
:In the non-WYSIWYG editor, can be used to build a basic COinS tag. (P. Binkley)
:This was abandoned in favor of the generator at http://generator.ocoins.info/. However, the generator has now gone south and no longer seems to be supported.

===Presentation===
;[http://www.viper007bond.com/wordpress-plugins/syntaxhighlighter/ SyntaxHighlighter Evolved]
:Post syntax-highlighted code.
;C4LJ Custom the_author()
:Replaces the text returned by the_author() with the value of the "author" custom field. Necessary since articles are entered by their editors, but we want author information to appear on the articles and in the syndication feeds.

===User Feedback===
;[http://contactform7.com/ Contact Form 7]
:Email contact form plugin.
;[http://www.callum-macdonald.com/code/wp-mail-smtp/ WP-Mail-SMTP]
:Reconfigures the wp_mail() function to use SMTP instead of mail() and creates an options page to manage the settings.

===URLs===
;C4LJ Remove Parents
:A customization of http://wordpress.org/extend/plugins/remove-parents/. Prettifies category URLs so that issues appear at <code>http://journal.code4lib.org/issues/issue1</code> instead of <code>http://journal.code4lib.org/issues/issues/issue1</code>. (J. Brinley)
;[http://www.feedburner.com/fb/a/help/wordpress_quickstart FeedBurner FeedSmith]
:Redirects the main feed and the general comments feed to FeedBurner

===Workflow===
;[https://github.com/code4lib/c4lj-issue-manager Issue Manager]
:Enables one-click publishing of new issues, and prevents articles from being published until their associated issue is published. (J. Brinley)
;[http://wordpress.org/extend/plugins/revision-cleaner/ Revision Cleaner]
:Auto clean your revisions that you don't needed any more.
;[http://www.im-web-gefunden.de/wordpress-plugins/role-manager/ Role Manager]
:Allows creation of custom roles and editing of roles' permissions. Used to create the Reviewer role, which can read Private articles, so that authors can see their articles before publication, and to prevent editors from publishing articles on accident.
;C4LJ Permissions
:Lets authors see pending posts. (J. Brinley)
;C4LJ Remove Parents
:Remove parent directories & "category" from category permalinks. (J. Brinley)
;Remove Special Word Characters
:Replaces special characters copied from MS Word with their entity equivalents. (J. Brinley)

==Upgrading==

==="Submit for Review"===
Edit wp-admin/includes/post.php. After line 71 (in version 2.3.3) add:
// START FIX
if ('publish' == $_POST['post_status'] && !current_user_can( 'publish_posts' )) {
$post =& get_post( $post_ID );
if ('publish' != $post->post_status)
$_POST['post_status'] = 'pending';
}
// END FIX

==Issue Manager Plugin==
===To Publish an Issue===
#Assign timestamps to the articles in the order you want them to appear on the page (newest timestamps go at the top of the page)
#Go to the Issue Manager page in the "Manage" tab.
#Click "Publish" next to the category for the issue you want to publish.
#All "Pending Review" articles with the given category (that don't also have an "unpublished" category) will be published, with the timestamps updated to about now, retaining the order established earlier.
===To Prevent Early Publication of Articles===
#Go to the Issue Manager page in the "Manage" tab.
#Click "Unpublish" next to the category for the issue you want to keep unpublished.
#Any published articles with that category will revert to "Pending Review" status. Any new articles you attempt to publish will instead be set to "Pending Review".

==Google Code Repository==
The theme and plugins used by the Journal are available via [http://code.google.com/p/c4lj/ Google Code]. Some of the plugins are described on [http://xplus3.net/tag/plugins/ Jonathan Brinley's blog].

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2014-07-22T14:35:36Z

Dbs: /* Publishing an Issue */

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in the 'Administrivia' tab/worksheet of our Google Docs article tracking spreadsheet.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html.
Fortunately, WP has a built-in feature to help with this.
Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon.
This transforms Word's html into really nice pretty html.
Alternatively, use the [http://www.textfixer.com/html/convert-word-to-html.php Word DOC to HTML converter].

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to login.ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

==== Video ====

We haven't had too much video, but we just had one (a screencast). The option we used was hosting on archive.org. Upload the video, click on the IA 'pillars' icon on the resulting video on the archive.org page to get an 'iframe' embed code, which works fine in our wordpress html source, and I believe the archive.org infrastructure will take care of translating the video to multiple formats and delivering in the proper format for a given browser. Very convenient.

Include a visible link to the archive.org URL for the individual video page as a caption, so printed or otherwise captured versions of the article will always have that link.

You don't need to use archive.org if you or we figure out a better way, it's just one option that worked very conveniently so far.

===Code===

If code is attached as a file, follow the directions above for attached images, except:

* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). Around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work). If the language parameter is not set, it will default to "text" (no syntax highlighting). For a full list consult: http://en.support.wordpress.com/code/posting-source-code/

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|Text||text (e.g. .conf file)
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
[sourcecode language='css']
body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}
[/sourcecode]

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

Abstracts should be placed in the Excerpt box, displayed a little ways below the "Post" field. If you do not see the Excerpt box, look under "Screen Options" in the top right of the page. Selecting the down arrow will display fields to show on the screen. Make sure that 'Excerpt' is selected. This will display the Excerpt (abstract) input box on the page.

Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
# Update [http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor] on the Editorial Committee page to state the name of the editor for the next issue.

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

Code4Lib Journal WordPress Input Guidelines

2014-07-22T14:34:49Z

Dbs: Publishing an Issue - update the name of the next coordinating editor

Please follow the guidelines below when creating or editing Code4Lib Journal articles in WordPress. Enter all articles as "Posts".

==The WP Admin Interface==
To get to WordPress interface for entering an article, choose 'Site Admin' from the footer of any Journal page, login if necessary, and then choose Write//Write Post from the WP admin menus. (Alternatively, go to http://journal.code4lib.org/wp-admin/). If you don't have a WordPress editor login and need one, talk to our web admin (Jon Brinley).

==Proofs for Authors==
A read-only login that is shared with authors can be found in the 'Administrivia' tab/worksheet of our Google Docs article tracking spreadsheet.

==Title==
Title, including the subtitle, goes in the "Title" field.

==Article Content==
The body of the article goes in the "Post" field. The top-level header (<code><h1></code>) is used for the title of the post, so start with second-level headers (<code><h2></code>) for sections of the article. Any header from second- to sixth-level may be used as appropriate. Use HTML markup appropriately and semantically, ''e.g.'', <code><em></code> for emphasized text, <code><strong></code> for strongly emphasized text, <code><blockquote></code> when quoting blocks of text. Avoid such monstrosities as <code><font></code> and <code><blink></code>.

===Pasting from Word===

If you just paste content from Word into WP, it ends up with REALLY BAD html.
Fortunately, WP has a built-in feature to help with this.
Open the 'advanced toolbar' in editing GUI (right-most link), then click on the paste-from-word icon.
This transforms Word's html into really nice pretty html.
Alternatively, use the [http://www.textfixer.com/html/convert-word-to-html.php Word DOC to HTML converter].

===Images and Attached Content===
In-line images should be no wider than 500px.

The caption for an image should be entered in a p with class="caption":
<nowiki><p class="caption">Figure 1. How to Caption an Image.</p>
</nowiki>
In general, we bold the figure / table label using the strong tag:
<nowiki><p class="caption"><strong>Figure 1.</strong> How to Caption an Image.</p>
</nowiki>

'''Uploading files manually'''

To upload images or other attached media / files, you will need to upload the content to our ibiblio host site manually.

To do that, sftp to login.ibiblio.org. See the Administrivia tab in the shared "C4LJ Article Tracking" doc for the username and password.

Change directory to:
/public/vhost/c/c4lj/html/media

in there you'll find an "issue1" subdir (or issueX subdir--if you don't, create one or ask for help creating one!). Inside THERE, create a subdir with the last name of the first author, and put all your image and other attached content in there. It will now have this sort of url:
http://journal.code4lib.org/media/issue1/smith/imagename.png

Add to your img src or a href's as desired. You can use this not just for images, but for extended code attachments, etc. (see below)

'''Uploading media via WordPress'''

Before uploading files to WordPress, you will need to change permissions on the directory where you are putting the files.
# Login to c4ljeditor@login.ibiblio.org. Ask jrochkind for the password for the c4ljeditor account (or see this [http://groups.google.com/group/c4lj-articles/msg/fad004416f12ac25 post] on c4lj-articles).
# Change the directory to /public/vhost/c/c4lj/html/wp-content/uploads/
# WordPress tries to write the files to /public/vhost/c/c4lj/html/wp-content/uploads/[current year]/[current month]. If the current year or month directory does not yet exist, create them, "mkdir [current year]" or mkdir "[current month]" in the appropriate directory. Creating the directory while logged in makes the owner and group of the directory c4ljeditor and c4lj respectively. Wordpress will create the directories as nobody/nobody.
# Change the permissions on the [current month] directory from 755 to 777, "chmod 777 [current month]".
# In the WordPress editor, click the "Add an Image" button.
# Browse to and select your image/file.
# Click the Upload button.
# File in the Alternate text and Caption fields.
# Select the size of the image you want to display in the article.
# Click "Insert into Post".
# On the ibiblio.org server, change the permissions on the current month's directory back to 775, "chmod 775 [current month]"

==== Video ====

We haven't had too much video, but we just had one (a screencast). The option we used was hosting on archive.org. Upload the video, click on the IA 'pillars' icon on the resulting video on the archive.org page to get an 'iframe' embed code, which works fine in our wordpress html source, and I believe the archive.org infrastructure will take care of translating the video to multiple formats and delivering in the proper format for a given browser. Very convenient.

Include a visible link to the archive.org URL for the individual video page as a caption, so printed or otherwise captured versions of the article will always have that link.

You don't need to use archive.org if you or we figure out a better way, it's just one option that worked very conveniently so far.

===Code===

If code is attached as a file, follow the directions above for attached images, except:

* If there is not a folder for the author, create it, according to the guidelines above for images)
* Create a subfolder under the author's folder for "code". Insert code files here
* In the article link to the files using the path format http://path-to-the-server/media/issueNumber/authorname/code/filename (e.g., http://journal.code4lib.org/media/issue1/smith/code/something.pl)

Put all inline code in <code><pre></code> tags.

====Code Highlighting====

If the code is in a supported language, we can do syntax highlighting.

ibiblio has a PHPS extensionm, so if you an "s" on the end of .php files, e.g.,
<filename>.phps
it does syntax highlighting for you.

We're still deciding if we like the syntax highlighting, don't feel compelled to make it work if it's not working for you (but please let other editors know what your experience is). Around your code, include
[sourcecode language='langcode']...[/sourcecode]

Replace <code>langcode</code> with the appropriate code from the following list (if more than one option for a language, any one will work). If the language parameter is not set, it will default to "text" (no syntax highlighting). For a full list consult: http://en.support.wordpress.com/code/posting-source-code/

{|
!Language!!Code
|-
|C++||cpp, c, c++
|-
|C#||c#, c-sharp, csharp
|-
|CSS||css
|-
|Delphi||delphi, pascal
|-
|Java||java
|-
|JavaScript||js, jscript, javascript
|-
|PHP||php
|-
|Python||py, python
|-
|Ruby||rb, ruby, rails, ror
|-
|SQL||sql
|-
|Text||text (e.g. .conf file)
|-
|VB||vb, vb.net
|-
|XML/HTML||xml, html, xhtml, xslt
|}

Example:
[sourcecode language='css']
body {
font-size: 0.625em;
background-color: #0000ff;
color: #ffff00;
}
[/sourcecode]

====Ampersand Issues====
We've had some problems with ampersand handling in the sourcecode sections. If you notice extra amp;s in your article, such as "&amp;amp;" and "&amp;amp;amp;", and you're comfortable using only the HTML editor for article entry, try checking the "Disable the visual editor when writing" box on your profile page in the admin.

==Abstract==

Abstracts should be placed in the Excerpt box, displayed a little ways below the "Post" field. If you do not see the Excerpt box, look under "Screen Options" in the top right of the page. Selecting the down arrow will display fields to show on the screen. Make sure that 'Excerpt' is selected. This will display the Excerpt (abstract) input box on the page.

Use HTML markup as appropriate. What you put in this field is what will be distributed in our syndication feed and what will appear before the article as the abstract.

Assigned editors are ultimately responsible for a good abstract. Authors aren't always the best at writing good abstracts for their articles, you should probably revise or even write a new one from scratch as necessary, even when the author has provided one. Some of the abstracts for my assigned articles haven't even mentioned what I consider the most significant features of the article.

Since indexes (like EBSCO) may end up indexing abstracts and not full text (and even full text indexes may weigh abstracts more highly), the abstract should probably include any important terms that should 'hit' on the article, such as key technologies or concepts.

I've found that extracting sentences or clauses from the article itself is a good way to build an abstract that will represent the article as the authors intended. The conclusion section is often a good place to look for such key sentences/clauses.

Final abstracts should be passed by the authors for approval.

==Bibliographies/Endnotes==
We would like to provide COinS information with every appropriate citation that does not have a publically accessible url.
* Recommended COinS generator: http://generator.ocoins.info/ .
** If using this generator, enter '(COinS)' in the box for COinS Default Text and 'http://journal.code4lib.org/coins' in the box for COinS Default Link at the bottom.
** Paste the output provided at the end of the reference in HTML. You will need to delete the line breaks inserted into the output created by the generator for it to work properly.
* Another option is to use the WP COinS plugin. Open the Code tab, put the cursor before the citation, and click COinS. Enter the appropriate information. This works so-so for journals, and not at all for books.
* COinS should really always have an ISSN or ISBN.
* Inside the span tag, put the string "(COinS)" with a link to our coins explanation page. Ie:

<pre><a href="http://journal.code4lib.org/coins">(COinS)</a></pre>

This is so the user without a browser extension will see that something is there she might be interested in, and get an explanation of COinS and how to make use of it.

===Endnotes style and HTML coding===
* Endnote number in text: The number is the link which appears in square brackets. Square brackets themselves are not part of the link. HTML coding for the text: '''[<a id="ref1" href="#note1">1</a>]'''

* The link should work both ways. So, the endnote will link back to the text. HTML coding for the endnote: '''[<a id="note1" href="#ref1">1</a>]'''

==Author Information==

Start off each article with a paragraph stating the name(s) of the author(s). Something simple like "By Jonathan Rochkind". If desired, the author's name can be a link to something appropriate.

End each article with a second-level header that says "About the Author(s)", with class="abouttheauthor" set. Then give a short paragraph about each author. We do want to have some kind of contact information published (personal web page, email address (obscured if desired), etc.) for each author.

There is a box beneath the article-editing box with the label "Author(s)". Anything you put in this field will be treated as the author of the article. This will show up in the ToC and in the syndication feeds. If you don't populate this field, WordPress will use the username of the editor, instead.

==Categories/Tags==
Posts will have "Uncagetorized" checked by default. Uncheck that box, and check the box next to the current issue, which will be a subcategory of "Issues." Do not check the "Issues" category. We generally do not add tags, except for Conference reviews

==WordPress Buttons==

;Save
:Saves the article, sets the post status to whatever option is selected in the Publish Status form.
;Publish
:Saves the article, sets the post status to Pending Review and assigns a timestamp to the article.

If an issue is not yet published, setting the post status to "Published" or clicking the "Publish" button will set the article to "Pending Review" status. If the issue is already published, this would actually publish the article.

==WordPress Post Status==
An article has four possible statuses. However, only the first three statuses are available to editors.
;Draft
:Use for not yet complete articles. Only editors can see these.
;Pending Review
:Use for sharing the article with authors. Editors and anyone logged in with user ID 17 (i.e., the author account) can see these. See this [http://groups.google.com/group/c4lj-articles/browse_thread/thread/1231b06c09f1289f post] on c4lj-articles for the login information for the author account (username: author).
;Private
:We don't use this option anymore.
;Published
:A published post is visible to everyone. It is part of the RSS feed. If you're editing an already published post, don't select anything in the post status form, just hit Save.

==Publishing an Issue==

# Let everyone on the c4lj-articles list know you are getting ready to publish (so they can save and close any open articles).
# Log in to WordPress
# Make sure that all articles for the issue have the correct issue category selected and have been set to 'Pending Review'. Make sure that the "Uncategorized" and "Issues" categories are unchecked (only the specific issue should be selected).
# Sanity check: count the number of posts which should appear in the publish list
# Click on Posts -> Issues (on the left side)
# Click on "Publish" for the issue you'd like to publish.
## You'll get a list of every "Pending Review" article in that issue. Make sure the number of articles in the list matches your previous count. Don't see all the articles you think you should see? They could be still in Draft status, or not in the correct Issue category, or still have "Uncategorized" selected, or someone may still have it in edit mode. Go back to the posts list and make any necessary changes, and start from #5 again.
# Drag and drop the article titles until they're in the order you want. The order you see there is the order you'll see on the home page (and probably the opposite of the order you'll see in your feed reader).
## Note: It's the coordinating editor's responsibility to decide what order he or she would like the articles to show up in, and order them appropriately when publishing the issue. In general, we try to put the articles with the widest appeal first, and special types (columns, special reports, book reviews, etc.) at the end.
# Click on Posts -> Categories (on the left side)
# Make sure all three fields for the current issue are filled in and correct:
## The human-readable name of the issue goes into the Name field -- e.g., "Issue 15".
## The date of publication goes into the Description field -- e.g., "2011-10-31".
## The URL name goes into the Slug field -- e.g., "issue15" would give the URL of the issue, http://journal.code4lib.org/issues/issue15
# Click "Publish Issue" (optionally setting the publication time, first). Setting the time should only have an impact on readers who are not logged into the c4lj site. Editors will be able to see the published articles.
# Go to the Journal front page; check the number of articles is correct (again) and that they are in the right order. If there is a problem, go back to the admin interface, click on Posts -> Issues and click Unpublish for the issue. Make whatever corrections are needed and proceed from #5 again.
# Once the issue is finally published, go to [[Code4Lib_Journal_Entries_in_Directory_of_Open_Access_Journals]] and follow the directions to upload the issue metadata to DOAJ.
# Send out announcements (see [[Code4Lib_Journal_Publicity_Venues]])
# Update [[http://journal.code4lib.org/editorial-committee#coordinating Coordinating Editor]] to list the name of the editor for the next issue.

==Corrections==
See [http://groups.google.com/group/c4lj-articles/browse_thread/thread/8eaabcff2d9c000d/a0aeeb9367fcea5f?lnk=gst&q=errata#a0aeeb9367fcea5f|the editors' list] for how to make corrections. Generally, use an Errata or Correction section at the end with information about the change that was made and have the actual text link down to that section. See also [[Code4Lib_Corrections]]

[[Category:Code4Lib Journal]]

2014 Links from Talks

2014-03-31T21:20:02Z

Dbs: /* Structured Data NOW: seeding schema.org in library systems */

== What's this page ==

Making a page for links mentioned in talks. Sadly, started it halfway through conference and network is flaky, but will try to go back.

Tuesday, March 25

== Welcome to Code4Lib 2014 ==
Tim McGeary, Code4Lib 2014 Conference Co-Chair and Director of Library & Information Technology at UNC-Chapel Hill

== Opening Keynote ==
Sumana Harihareswara

http://wiki.code4lib.org/index.php/2014_Keynote_by_Sumana_Harihareswara

== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina’s Book Viewer Framework Makes it Possible ==
Engy Morsy

== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==
Bohyun Kim

== WebSockets for Real==Time and Interactive Interfaces ==
Jason Ronallo

== Personalize Your Google Analytics Data with Custom Events and Variables ==

Josh Wilson

*[https://www.dropbox.com/s/dpxnffoenmpyh7d/Personalizing%20Google%20Analytics.pdf Slides (PDF)] | [https://docs.google.com/presentation/d/1vmCgMRr4-wJJqiPS2vA9K6JLGtsxRgOMsXhdqqcqz7E/edit?usp=sharing Slides (Google Docs)]
*[https://github.com/joshwilsonnc/ga_cdm Code for recording CONTENTdm 6 metadata fields as Events (Github)]
*Questions? joshwilsonnc at gmail.

== Discovering your Discovery System in Real Time ==
Godmar Back and Annette Bailey

== Structured Data NOW: seeding schema.org in library systems ==

* [http://stuff.coffeecode.net/2014/structured_data_now The presentation itself]
* [http://www.w3.org/TR/rdfa-lite/ RDFa Lite 1.1 W3C recommendation] - one of the only W3C specifications that acts like a single-page, clearly written, easily understood tutorial. It's marvellous!
* [http://schema.org schema.org official web site]
* [http://stuff.coffeecode.net/2014/schema_org_codelab/ schema.org hands-on code lab] - teaches you step by step how to add schema.org to a web page using RDFa
* [http://www.w3.org/community/schemabibex/ W3C Schema Bib Extend Community Group] - best practices for schema.org bibliographic use cases, extension proposals in progress, mailing list for assistance

Dan Scott

== Next Generation Catalogue - RDF as a Basis for New Services ==
Anne-Lena Westrum, Benjamin Rokseth, Asgeir Rekkavik, and Petter Goksøyr Åsen

== More Like This: Approaches to Recommending Related Items using Subject Headings ==
Kevin Beswick

== Breakout Sessions I (no breakout report, but please select a recorder and post the report to the wiki) ==

== Lightning Talks I ==

Wednesday, March 26

# ResCarta Foundation
## [http://www.rescarta.org rescarta.org]
# Arie Nugraha: SLiMS: Indonesia Grassroot Libraries Revolution]
## [https://drive.google.com/file/d/0BzZt7DLxfV4Xd05lTXBjb0xQdGc/edit?usp=sharing SLiMS: Indonesia Grassroot Libraries Revolution - Slide links]
## [http://slims.web.id SLiMS Site page]
## [https://github.com/slims/slims7_cendana Github page]
# Harvard Library Lab (Bobbi Fox)
# Logs Are Your Friend (Rosalyn Metz)
# Solr Browse & Sort (Michael Gibney)
# GeoHydra (Darren Hardy)

== Visualizing Solr Search Results with D3.js for User==Friendly Navigation of Large Result Sets ==
Julia Bauder

== Visualizing Library Resources as Networks ==
Matt Miller

== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==
Cynthia Ng

== Dead-simple Video Content Management: Let Your Filesystem Do The Work ==
Andreas Orphanides

http://www.dropbox.com/sh/ogo7su7shn0zegt/Ttv_5o_QZg

== Lightning Talks 2 ==

Proxy Authentication with Google Open ID

Paired Programming

* [http://scholarsphere.psu.edu/files/6395w812z Slides]
* [http://www.extremeprogramming.org/rules/pair.html Source of quote about pair programming]

Mx Matienzo - "Dial-A-DPLA":

* [http://matienzo.org/storage/2014/2014Mar-code4lib-lightning-talk/ Slides]
* [https://github.com/anarchivist/dial-a-dpla Code]
* [http://twilio.com/ Twilio]
* [https://github.com/RobSpectre/Twilio-Hackpack-for-Heroku-and-Flask Twilio hackpack for Heroku and Flask]
* [http://labs.cooperhewitt.org/2013/object-phone/ Cooper-Hewitt's "Object Phone"]

Copy, Paste & Search (Cory Lown)

qstat (Hillel Arnold)

Add map view to Your Blacklight app (Jack Reed)

Drupal 8: Of Course (Cary Gordan)

LTI Protocol + Discovery API (LMS <3)

File Analyzer (Terry Brady)
*[http://scholarsphere.psu.edu/files/6395w812z File Analyzer Documentation]

Highcharts JS (Heather RayL)

jQuery.xmleditor

This is my Search (Cynthia "Arty" Ng)

*

== Bulding for others (and ourselves): the Avalon Media System ==
Michael B. Klein and Julie Rudder

== Sustaining your Open Source project through training ==
Bess Sadler and Mark Bussey

== Behold Fedora 4: The Incredible Shrinking Repository! ==
Esmé Cowles

== A reusable application to enable self deposit of complex objects into a digital preservation environment ==
Jill Sexton, Mike Daines, and Greg Jansen

== Breakout Sessions 2 (no breakout report; but please select a recorder and post the report on the wiki)

== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==
Steve Meyer and Karen Coombs

Slides: http://www.oclc.org/resources/developer-network/PPTs/consumable-APIs-coombs-meyer.pptx

== Towards Pasta Code Nirvana: Using Javascript MVC to Fill Your Programming Ravioli ==
Bret Davidson

== PhantomJS+Selenium: Easy Automated Testing of AJAX-y UIs ==
Martin Haye and Mark Redar

http://bit.ly/c4lphantom

== Queue Programming -- how using job queues can make the Library coding world a better place ==
Birkin James Diana

Thursday, March 27

== Closing Keynote - An Interview with Valerie Aurora ==

== Lightning Talks ==
Bplgeo: A Gem to Process Geographic Data / Steven Anderson

Frog Boiling / Charlie Morris & Angie Fullington
* [http://www.slideshare.net/cdmorris22/frogboil Slides]

Dev Ops @ PSU / Justin Patterson

MozSuite Webmastery, Software Carpentry, Privacy, & Archives / Jeannie Rose Halperin

Mass Digitization / Tim Shearer

Schema.org + Google CSE + Local Search / Sean Aery

Chicago Collections Consortium / Tracy Seneca & Kate Flynn

Contrary Technologies / Ian Walls

Browse-Everything for Rails

== Under the Hood of Hadoop Processing at OCLC Research ==
Roy Tennant

== Lucene’s Latest (for Libraries) ==
Erik Hatcher

== All Tiled Up ==
Mike Graves

2014 Links from Talks

2014-03-31T21:13:56Z

Dbs: /* Structured Data NOW: seeding schema.org in library systems */

== What's this page ==

Making a page for links mentioned in talks. Sadly, started it halfway through conference and network is flaky, but will try to go back.

Tuesday, March 25

== Welcome to Code4Lib 2014 ==
Tim McGeary, Code4Lib 2014 Conference Co-Chair and Director of Library & Information Technology at UNC-Chapel Hill

== Opening Keynote ==
Sumana Harihareswara

http://wiki.code4lib.org/index.php/2014_Keynote_by_Sumana_Harihareswara

== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina’s Book Viewer Framework Makes it Possible ==
Engy Morsy

== Quick and Easy Data Visualization with Google Visualization API and Google Chart Libraries ==
Bohyun Kim

== WebSockets for Real==Time and Interactive Interfaces ==
Jason Ronallo

== Personalize Your Google Analytics Data with Custom Events and Variables ==

Josh Wilson

*[https://www.dropbox.com/s/dpxnffoenmpyh7d/Personalizing%20Google%20Analytics.pdf Slides (PDF)] | [https://docs.google.com/presentation/d/1vmCgMRr4-wJJqiPS2vA9K6JLGtsxRgOMsXhdqqcqz7E/edit?usp=sharing Slides (Google Docs)]
*[https://github.com/joshwilsonnc/ga_cdm Code for recording CONTENTdm 6 metadata fields as Events (Github)]
*Questions? joshwilsonnc at gmail.

== Discovering your Discovery System in Real Time ==
Godmar Back and Annette Bailey

== Structured Data NOW: seeding schema.org in library systems ==

Presentation: http://stuff.coffeecode.net/2014/structured_data_now

Dan Scott

== Next Generation Catalogue - RDF as a Basis for New Services ==
Anne-Lena Westrum, Benjamin Rokseth, Asgeir Rekkavik, and Petter Goksøyr Åsen

== More Like This: Approaches to Recommending Related Items using Subject Headings ==
Kevin Beswick

== Breakout Sessions I (no breakout report, but please select a recorder and post the report to the wiki) ==

== Lightning Talks I ==

Wednesday, March 26

# ResCarta Foundation
## [http://www.rescarta.org rescarta.org]
# Arie Nugraha: SLiMS: Indonesia Grassroot Libraries Revolution]
## [https://drive.google.com/file/d/0BzZt7DLxfV4Xd05lTXBjb0xQdGc/edit?usp=sharing SLiMS: Indonesia Grassroot Libraries Revolution - Slide links]
## [http://slims.web.id SLiMS Site page]
## [https://github.com/slims/slims7_cendana Github page]
# Harvard Library Lab (Bobbi Fox)
# Logs Are Your Friend (Rosalyn Metz)
# Solr Browse & Sort (Michael Gibney)
# GeoHydra (Darren Hardy)

== Visualizing Solr Search Results with D3.js for User==Friendly Navigation of Large Result Sets ==
Julia Bauder

== Visualizing Library Resources as Networks ==
Matt Miller

== We Are All Disabled! Universal Web Design Making Web Services Accessible for Everyone ==
Cynthia Ng

== Dead-simple Video Content Management: Let Your Filesystem Do The Work ==
Andreas Orphanides

http://www.dropbox.com/sh/ogo7su7shn0zegt/Ttv_5o_QZg

== Lightning Talks 2 ==

Proxy Authentication with Google Open ID

Paired Programming

* [http://scholarsphere.psu.edu/files/6395w812z Slides]
* [http://www.extremeprogramming.org/rules/pair.html Source of quote about pair programming]

Mx Matienzo - "Dial-A-DPLA":

* [http://matienzo.org/storage/2014/2014Mar-code4lib-lightning-talk/ Slides]
* [https://github.com/anarchivist/dial-a-dpla Code]
* [http://twilio.com/ Twilio]
* [https://github.com/RobSpectre/Twilio-Hackpack-for-Heroku-and-Flask Twilio hackpack for Heroku and Flask]
* [http://labs.cooperhewitt.org/2013/object-phone/ Cooper-Hewitt's "Object Phone"]

Copy, Paste & Search (Cory Lown)

qstat (Hillel Arnold)

Add map view to Your Blacklight app (Jack Reed)

Drupal 8: Of Course (Cary Gordan)

LTI Protocol + Discovery API (LMS <3)

File Analyzer (Terry Brady)
*[http://scholarsphere.psu.edu/files/6395w812z File Analyzer Documentation]

Highcharts JS (Heather RayL)

jQuery.xmleditor

This is my Search (Cynthia "Arty" Ng)

*

== Bulding for others (and ourselves): the Avalon Media System ==
Michael B. Klein and Julie Rudder

== Sustaining your Open Source project through training ==
Bess Sadler and Mark Bussey

== Behold Fedora 4: The Incredible Shrinking Repository! ==
Esmé Cowles

== A reusable application to enable self deposit of complex objects into a digital preservation environment ==
Jill Sexton, Mike Daines, and Greg Jansen

== Breakout Sessions 2 (no breakout report; but please select a recorder and post the report on the wiki)

== Organic Free-Range API Development - Making Web Services That You Will Actually Want to Consume ==
Steve Meyer and Karen Coombs

Slides: http://www.oclc.org/resources/developer-network/PPTs/consumable-APIs-coombs-meyer.pptx

== Towards Pasta Code Nirvana: Using Javascript MVC to Fill Your Programming Ravioli ==
Bret Davidson

== PhantomJS+Selenium: Easy Automated Testing of AJAX-y UIs ==
Martin Haye and Mark Redar

http://bit.ly/c4lphantom

== Queue Programming -- how using job queues can make the Library coding world a better place ==
Birkin James Diana

Thursday, March 27

== Closing Keynote - An Interview with Valerie Aurora ==

== Lightning Talks ==
Bplgeo: A Gem to Process Geographic Data / Steven Anderson

Frog Boiling / Charlie Morris & Angie Fullington
* [http://www.slideshare.net/cdmorris22/frogboil Slides]

Dev Ops @ PSU / Justin Patterson

MozSuite Webmastery, Software Carpentry, Privacy, & Archives / Jeannie Rose Halperin

Mass Digitization / Tim Shearer

Schema.org + Google CSE + Local Search / Sean Aery

Chicago Collections Consortium / Tracy Seneca & Kate Flynn

Contrary Technologies / Ian Walls

Browse-Everything for Rails

== Under the Hood of Hadoop Processing at OCLC Research ==
Roy Tennant

== Lucene’s Latest (for Libraries) ==
Erik Hatcher

== All Tiled Up ==
Mike Graves

Code4Lib Journal Deadlines

2014-03-10T18:07:36Z

Dbs: Issue 24 is over man, game over

''See also [[Code4Lib Journal Voting]]''

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

{| border="1" cellpadding="2" cellspacing="0"
|-
! Weeks before
! Task
! Day offset
! On
|-
| style="text-align:right" | '''-18'''
| Call for proposals
| style="text-align:right" | -126
| Monday
|-
| style="text-align:right" | '''-14'''
| Proposals due
| style="text-align:right" | -94
| Friday
|-
| style="text-align:right" | '''-13'''
| Publication of previous issue
| style="text-align:right" | -91
| Monday
|-
| style="text-align:right" | '''-13'''
| Finish voting on proposals; notify authors
| style="text-align:right" | -87
| Friday
|-
| style="text-align:right" | '''-9'''
| First draft due
| style="text-align:right" | -59
| Friday
|-
| style="text-align:right" | '''-5'''
| Second draft due
| style="text-align:right" | -31
| Friday
|-
| style="text-align:right" | '''0'''
| Publication
| style="text-align:right" | 0
| Monday
|}

'''Note:''' Week numbers assume week begins on Monday.

'''See also:''' [[Code4Lib_Journal_Email_Templates]] (formerly at [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses Templates for Email Responses])

== Deadlines for Issues ==
Editors: see also http://tomkeays.com/library/c4ljpubdate/ for Tom's calculator

===Twenty-seventh issue===
Coordinating editor for issue #27:

*Call for proposals: Monday, September 15, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 17, 2014
*Proposals accepted: Friday, October 24, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 13, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: '''Dan Scott'''

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
Coordinating editor for issue #24: Ron Peterson

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

Code4Lib Journal Deadlines

2014-03-10T18:07:08Z

Dbs: Dan Scott is in

''See also [[Code4Lib Journal Voting]]''

== Formula for calculating deadlines ==

A rough guideline based on recent issues:

{| border="1" cellpadding="2" cellspacing="0"
|-
! Weeks before
! Task
! Day offset
! On
|-
| style="text-align:right" | '''-18'''
| Call for proposals
| style="text-align:right" | -126
| Monday
|-
| style="text-align:right" | '''-14'''
| Proposals due
| style="text-align:right" | -94
| Friday
|-
| style="text-align:right" | '''-13'''
| Publication of previous issue
| style="text-align:right" | -91
| Monday
|-
| style="text-align:right" | '''-13'''
| Finish voting on proposals; notify authors
| style="text-align:right" | -87
| Friday
|-
| style="text-align:right" | '''-9'''
| First draft due
| style="text-align:right" | -59
| Friday
|-
| style="text-align:right" | '''-5'''
| Second draft due
| style="text-align:right" | -31
| Friday
|-
| style="text-align:right" | '''0'''
| Publication
| style="text-align:right" | 0
| Monday
|}

'''Note:''' Week numbers assume week begins on Monday.

'''See also:''' [[Code4Lib_Journal_Email_Templates]] (formerly at [http://groups.google.com/group/c4lj-articles/web/templates-for-email-responses Templates for Email Responses])

== Deadlines for Issues ==
Editors: see also http://tomkeays.com/library/c4ljpubdate/ for Tom's calculator

===Twenty-seventh issue===
Coordinating editor for issue #27:

*Call for proposals: Monday, September 15, 2014
*Second call for proposals: Monday, October 6, 2014 (if necessary)
*Proposals due: Friday, October 17, 2014
*Proposals accepted: Friday, October 24, 2014
*First draft due: Friday, November 21, 2014
*Second draft due: Friday, December 19, 2014
*Publication date: Monday, January 19, 2015

===Twenty-sixth issue===
Coordinating editor for issue #26: Kelley McGrath

*Call for proposals: Monday, June 9, 2014
*Second call for proposals: Monday, June 30, 2014 (if necessary)
*Proposals due: Friday, July 11, 2014
*Proposals accepted: Friday, July 18, 2014
*First draft due: Friday, August 15, 2014
*Second draft due: Friday, September 12, 2014
*Publication date: Monday, October 13, 2014

===Twenty-fifth issue===
Coordinating editor for issue #25: '''Dan Scott'''

*Call for proposals: Monday, March 10, 2014
*Second call for proposals: Monday, March 31, 2014 (if necessary)
*Proposals due: Friday, April 11, 2014
*Proposals accepted: Friday, April 18, 2014
*First draft due: Friday, May 16, 2014
*Second draft due: Friday, June 13, 2014
*Publication date: Monday, July 14, 2014

===Twenty-fourth issue===
'''Coordinating editor for issue #24: Ron Peterson'''

*Call for proposals: Monday, December 9, 2013
*Call for proposals #2: Monday, December 30, 2013 (if necessary)
*Proposals due: Friday, January 10, 2014
*Proposals accepted: Friday, January 17, 2014
*First draft due: Friday, February 14, 2014
*Second draft due: Friday, March 14, 2014
*Publication date: Monday, April 14, 2014

===Twenty-third issue===
Coordinating editor for issue #23: Shawn Averkamp
* Call for proposals: Monday, September 9, 2013
* Call for proposals #2: Monday September 30, 2013 (if necessary)
* Proposals due: Friday, October 11, 2013
* Proposals accepted: Friday, October 18, 2013
* First draft due: Friday, November 15, 2013
* Second draft due: Friday, December 13, 2013
* Publication date: Monday, January 13, 2014

===Twenty-second issue===
Coordinating editor for issue #22: Sara Amato
* Call for proposals: Monday, June 10, 2013
* Call for proposals #2: July 5, 2013 (if necessary)
* Proposals due: Friday, July 12, 2013
* Proposals accepted: Friday, July 19, 2013
* First draft due: Friday, August 16, 2013
* Second draft due: Friday, September 13, 2013
* Publication date: Monday, October 14, 2013

===Twenty-first issue===
Coordinating editor for issue #21: Terry Reese
* Call for proposals: Monday, March 11, 2013
* Call for proposals #2: Monday, April 1, 2013
* Proposals due: Friday, April 12, 2013
* Proposals accepted: Friday, April 19, 2013
* First draft due: Friday, May 17, 2013
* Second draft due: Friday, June 14, 2013
* Publication date: Monday, July 15, 2013

===Twentieth issue===
Coordinating editor for issue #20: [[User:DataGazetteer|Peter Murray]]
* Call for proposals:     Monday, December 10, 2012
* Call for proposals #2: Monday, January 7, 2013 (if necessary)
* Proposals due:          Friday, January 18, 2013
* Proposals accepted:     Friday, January 25, 2013
* First draft due:        Friday, February 22, 2013
* Second draft due:       Friday, March 22, 2013
* Publication date:       Monday, April 15, 2013

===Nineteenth issue===
Coordinating editor for issue #19: Andrew Darby
* Call for proposals: Monday, September 10, 2012
* Proposals due: Friday, October 12, 2012
* Proposals accepted: Friday, October 19, 2012
* First draft due: Friday, November 16, 2012
* Second draft due: Friday, December 14, 2012
* Publication date: Monday, January 14, 2013

===Eighteenth issue===
Coordinating editor for issue #18: Ron Peterson
* Call for proposals: Monday, May 28, 2012
* Proposals due: Friday, June 29, 2012
* Proposals accepted: Friday, July 6, 2012
* First draft due: Friday, August 3, 2012
* Second draft due: Friday, August 31, 2012
* Publication date: Monday, October 1, 2012

===Seventeenth issue===
Coordinating editor for issue #17: Tim Lepczyk
* Call for proposals: Wednesday, February 8, 2012
* Proposals due: Tuesday, February 28, 2012
* Proposals accepted: Tuesday, March 6, 2012
* First draft due: Tuesday, April 3, 2012
* Second draft due: Tuesday, May 1, 2012
* Publication date: Friday, June 1, 2012

===Sixteenth issue===
Coordinating editor for issue #16: Carol Bean
* Call for proposals: Monday, September 26, 2011
* Proposals due: Friday, October 28, 2011
* Proposals accepted: Friday, November 4, 2011
* First draft due: Friday, December 2, 2011
* Second draft due: Friday, December 30, 2011
* Publication date: Monday, January 30, 2012

===Fifteenth issue===
Coordinating editor for issue #15: Tod Olson
* Call for proposals: Monday, June 27, 2011
* Proposals due: Friday, July 29, 2011
* Proposals accepted: Friday, August 5, 2011
* First draft due: Friday, September 2, 2011
* Second draft due: Friday, September 30, 2011
* Publication date: Monday, October 31, 2011

===Fourteenth issue===

* Call for proposals: Monday, March 21, 2011
* Proposals due: Friday, April 22, 2011
* Proposals accepted: Friday, April 29, 2011
* First draft due: Friday, May 27, 2011
* Second draft due: Friday, June 24, 2011
* Publication date: Monday, July 25, 2011

===Thirteenth issue===

* Call for proposals: Monday, December 6, 2010
* Proposals due: Friday, January 7, 2011
* Proposals accepted: Friday, January 14, 2011
* First draft due: Friday, February 11, 2011
* Second draft due: Friday, March 11, 2011
* Publication date: Monday, April 11, 2011

===Twelfth issue===

* Call for proposals: Monday, August 16, 2010
* Proposals due: Friday, September 17, 2010
* Proposals accepted: Friday, September 24, 2010
* First draft due: Friday, October 22, 2010
* Second draft due: Friday, November 19, 2010
* Publication date: Monday, December 20, 2010

===Eleventh issue===

* Call for proposals: Monday, May 17, 2010
* Proposals due: Friday, June 18, 2010
* Proposals accepted: Friday, June 25, 2010
* First draft due: Friday, July 23, 2010
* Second draft due: Friday, August 20, 2010
* Publication date: Monday, September 20, 2010

=== Tenth issue ===

* Call for proposals: Monday, February 15, 2010
* Proposals due: Friday, March 19, 2010
* Proposals accepted: Friday, March 26, 2010
* First draft due: Friday, April 23, 2010
* Second draft due: Friday, May 21, 2010
* Publication date: Monday, June 21, 2010

=== Ninth issue ===

* Monday, November 9, 2009 -- Call for proposals
* Friday, December 11, 2009 -- Proposals due
* Friday, December 18, 2009 -- Finish voting on proposals, notify authors
* Friday, January 15, 2010 -- First draft due
* Friday, February 12, 2010 -- Second draft due
* Monday, March 15, 2010 -- Publication date

=== Eighth issue ===

* Monday, July 27 -- call for proposals
* Friday, August 14 -- proposals due
* Friday, August 21 -- finish voting on proposals; notify authors
* Friday, September 25 -- first draft due
* Friday, October 23 -- second draft due
* Monday, November 23 -- publication

=== Seventh issue ===

* Monday, February 16 -- call for proposals
* Friday, March 20 -- proposals due
* Monday, March 30 -- publication of issue 6
* Friday, March 27 -- finish voting on proposals; notify authors
* Friday, April 24 -- first draft due
* Friday, May 22 -- second draft due
* Monday, June 22 -- publication

=== Sixth issue ===

* Monday, November 10 -- call for proposals
* Friday, December 12 -- proposals due
* Monday, December 15 -- publication of issue 5
* Friday, December 19 -- finish voting on proposals; notify authors
* Friday, January 23 -- first draft due
* Friday, February 20 -- second draft due
* Monday, March 30 -- publication (originally scheduled for March 23)

=== Fifth issue ===

* Monday, August 18 -- call for proposals
* Friday, September 12 -- proposals due
* Friday, September 19 -- finish voting on proposals; notify authors
* Monday, September 22 -- issue 4 published
* Friday, October 17 -- first draft due
* Friday, November 14 -- second draft due
* Monday, December 15 -- publication

=== Fourth issue ===

* Friday, May 16 -- call for proposals
* Friday, June 20 -- extended proposal deadline (originally 6/13, before issue 3 is published)
* Friday, July 18 -- first draft due
* Friday, August 15 -- second draft due
* Monday, September 22 -- publication

=== Third issue ===

* Wednesday February 13th -- call for proposals
* Friday March 14th -- proposals due (after con, before issue 2)
* Friday April 25 -- first draft due
* Saturday June 21 -- publication (tentative)

=== Second issue ===

* Friday November 9th -- call for proposals
* Friday January 11 -- article draft deadline (or Thurs Jan 21, from EM)
* Thursday February 21 -- revisions/second draft deadline
* Friday March 21 -- publication (tentative)

=== First issue ===

* Friday August 31st -- call for proposals
* Friday October 12th -- article draft deadline
* Monday December 17th -- publication

[[Category: Code4Lib Journal]]

2014 preconference proposals

2014-01-14T19:42:58Z

Dbs: /* CLLAM @ code4lib */

= PROPOSALS ARE CLOSED : PLEASE DO NOT ADD NEW PRECONFERENCES TO THIS PAGE =

Proposals were accepted through December 6th, 2013.

It would be really, super duper helpful if folks who think they might want to attend a pre-conference could indicate interest by adding your name to a session below.

===Note===
Attendance at a pre-conference will require a small fee ''due at the time of conference registration".

Although this was specified in the email announcements relating to pre-conferences, it was not added to this page until December 2nd. I (Adam C.) apologize for the omission and I hope this will not cause any "sticker shock." Putting your name on this list does not incur any obligation on your part, but we'll be using it to gauge interest and work out room assignments.

Please put your pre-conference on the list in the following format:

=Code4Lib 2014 Pre-Conference Proposals=

===Drupal4lib Sub-con Barcamp===
=====Full Day=====

* Contact [[User:highermath|Cary Gordon]], cgordon@chillco.com

This will be a full day of self-selected barcamp style sessions. Anyone who wants to present can write down the topic on an index card and, after the keynote, we will vote to choose what we want to see. Attendees can also pick a topic and attempt to talk someone else into presenting on it.

This event is open to the library community. There will be a nominal fee (t/b/d) for non-Code4LibCon attendees (subject to organizer approval).

[[resources to help you learn drupal]]

====Interested in Attending:====

=====All Day=====

* Renna Tuten

=====Morning=====

* Kevin Reiss
* Charlie Morris (NCSU) - glad to see this again this year!
* Paula Gray-Overtoom
* Laurie Lee Moses

=====Afternoon=====

 

----

===Open Refine Hackfest===
'''"Half-Day"'''
* Contact [[User:bibliotechy|Chad Nelson]], chadbnelson@gmail.com

[http://openrefine.org/ Open Refine] is a powerful open source tool for wrangling messy data that can also be used to help in the creation of Linked Data via the [https://github.com/OpenRefine/OpenRefine/wiki/Reconciliation-Service-API Reconciliation API]. It is possible to write reconciliation services against API's, like the [http://iphylo.blogspot.com/2013/04/reconciling-author-names-using-open.html VIAF service] or, even just against local authority files for helping maintain authority control

The session would first introduce Open Refine, then walk through building a reconciliation service, and the rest of the session would be a hackfest where we build new reconciliation services for public consumption or local use.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
<ol>
<li>Adam Constabaris
<li>Ray Schwartz
<li>Jason Stirnaman
<li>Joshua Gomez
<li>Sam Kome
<li>Mike Beccaria
<li>Angela Zoss
<li>A. Soroka
<li> Matt Zumwalt
</ol>
----

===Responsive Design Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Jim Hahn, University of Illinois, jimfhahn@gmail.com
* Contact David Ward, University of Illinois, dh-ward@illinois.edu

This structured hackfest will give attendees an opportunity to explore methods to create responsive mobile apps using the Bootstrap framework [http://getbootstrap.com/]and a set of APIs for accessing library data. We will start with an API template for creating space-based mobile tools that draw from work coming out of the IMLS funded Student/Library Collaborative grant [http://www.library.illinois.edu/nlg_student_apps]. Available APIs will include a room reservation template and codebase for implementing at any campus and the set of Minrva catalog APIs generating JSONP [http://minrvaproject.org/services.php].

Hosts will give a brief report of a study on student hacking projects and interests in mobile library apps that are the basis for the templates utilized in this Hackathon. By the end of the pre-conference attendees will have a sample responsive mobile web app in Bootstrap 3 to bring back to their campus which can plug into their site-based content.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here
----

=== Intro to Blacklight ===
'''"Half-Day [Morning]"'''
* Contact: Chris Beer, Stanford University, cabeer@stanford.edu
* TA: Bess Sadler, Stanford University, bess@stanford.edu

This session will be walk-through of the architecture of Blacklight, the community, and an introduction to building a Blacklight-based application. Each participant will have the opportunity to build a simple Blacklight application, and make basic customizations, while using a test-driven approach.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ). We will also send out some brief instructions beforehand for those that would like to setup their environments to follow along and get Blacklight up and running on their local machines.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Megan Kudzia
# Bret Davidson
# Coral Sheldon-Hess
# Cory Lown
# Emily Daly
# Angela Zoss
# Sean Aery
# Francis Kayiwa
----

===Blacklight Hackfest===
'''"Half-Day [Afternoon]"'''
* Contact Chris Beer, Stanford University, cabeer@stanford.edu

This afternoon hackfest is both a follow-on to the Intro to Blacklight morning session to continue building Blacklight-based applications, and also an opportunity for existing Blacklight contributors and members of the Blacklight community to exchange common patterns and approaches into reusable gems or incorporate customizations into Blacklight itself.

For more information about Blacklight see our wiki ( http://projectblacklight.org/ ) and our GitHub repo ( https://github.com/projectblacklight/blacklight ).

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Shaun Ellis
# Kevin Reiss
# Megan Kudzia
# Erik Hatcher
# Emily Daly
# Laurie Lee Moses
# Francis Kayiwa

----

===RailsBridge: Intro to programming in Ruby on Rails===
'''"Half-Day" [morning]'''
* Contact Justin Coyne, Data Curation Experts, justin@curationexperts.com

Interested in learning how to program? Want to build your own web application? Never written a line of code before and are a little intimidated? There's no need to be! RailsBridge is a friendly place to get together and learn how to write some code.

RailsBridge is a great workshop that opens the doors to projects like Blacklight and Hydra.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

1. Ayla Stein

2. Heidi Dowding

3. Caitlin Christian-Lamb

4. Scott Bacon

5. [[User:RileyChilds | Riley Childs]]

6. Carolina Garcia

----

===Managing Projects: Or I'm in charge, now what? (aka PM4Lib)===
'''Full-Day'''

Contact:
* [[User:rosy1280|Rosalyn Metz]], rosalynmetz@gmail.com
* [[User:yoosebj|Becky Yoose]], yoosebec@grinnell.edu

This will be a full day session on project management. We'll cover
* '''Kicking off the Project''' -- project lifecycle, project constraints, scoping/goals, stakeholders, assessment
* '''Planning the Project''' -- project charters, work breakdown structures, responsibilities, estimating time, creating budgets
* '''Executing the Project''' -- status meeting, status reports, issue management
* '''Finishing the Project''' -- achieving the goal, post mortems, project v. product
This is a revival of rosy1280's LITA Forum Pre-Conference, but better (because iteration is good) and adapted to c4lib types.

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Robin Dean
# Erin White
# Andrew Darby
# Sam Kome
# Ryan Scherle
# Will Shaw
# Liz Milewicz
# Cynthia "Arty" Ng
# Laurie Lee Moses (if I don't do the Hackfest for Blacklight)
# Ranti Junus
# Bohyun Kim (Afternoon)

----

===Fail4Lib 2014===
'''Half Day [TBD, probably afternoon]'''

Contacts:
* Andreas Orphanides, akorphan (at) ncsu.edu
* Jason Casden, jmcasden (at) ncsu.edu

The task of design (and the work that we do as library coders) is intimately tied to failure. Failures, both big and small, motivate us to create and improve. Failures are also occasionally the result of our work. Understanding and embracing failure, encouraging enlightened risk-taking, and seeking out opportunities to fail and learn are essential to success in our field. At Fail4Lib, we'll talk about our own experiences with projects gone wrong, explore some famous design failures in the real world, and talk about how we can come to terms with the reality of failure, to make it part of our creative process -- rather than something to be feared.

The schedule may include the following:

* Case studies. We'll look at some classic failures from the literature: What can we learn from the mistakes of others?
* Confessionals, for those willing to share. Talk about your own experiences with rough starts, labor pains, and doomed projects in your own work: What can we learn from our own (and each others') failures?
* Group therapy. Let's talk about how to deal with risk management, failed projects, experimental endeavors, and more: How can we make ourselves, our colleagues, and our organizations more fault tolerant? How do we make sure we fail as productively as possible?

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Bret Davidson
#Mike Graves
#Ray Schwartz
#Jason Stirnaman
#Julia Bauder
#Linda Ballinger
#Scott Hanrath
#Caitlin Christian-Lamb
#Ian Walls
#Scott Bacon
#mx matienzo

----

===CLLAM @ code4lib===
'''(Computational Linguistics for Libraries, Archives and Museums)'''

'''Full Day'''

Contacts:
* Douglas W. Oard (primary), oard (at) umd.edu
* Corey Harper, corey (dot) harper (at) nyu.edu
* Robert Sanderson, azaroth42 (at) gmail.com
* Robert Warren, rwarren (at) math.carleton.ca

We will hack at the intersection of diverse content from Libraries, Archives and Museums and bleeding edge tools from computational linguistics for slicing and dicing that content. Did you just acquire the email archives of a startup company? Maybe you can automatically build an org chart. Have you got metadata in a slew of languages? Perhaps you can search it all using one query. Is name authority control for e-resources getting too costly? Let’s see if entity linking techniques can help. These are just a few teasers.

There’ll be plenty of content and tools supplied, but please bring your own [data] too -- you’ll hack with it in new ways throughout the day. We’ll get started with some lightning talks on what we’ve brought,then we’ll break up into groups to experiment and work on the ideas that appeal. Three guaranteed outcomes: you’ll walk away with new ideas, new tools, and new people you’ll have met.

''Interested in attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Devon Smith
# Kevin S. Clarke
# Jason Stirnaman
# Joshua Gomez
# Carolina Garcia
# Tom Burton-West
# Dan Scott
----

=== GeoHydra: Managing geospatial content ===

'''Half-day [Afternoon]'''

* Contact: Darren Hardy, Stanford University, drh@stanford.edu
* Moderator: Bess Sadler, Stanford University, bess@stanford.edu

Do you have digitized maps, GIS datasets like Shapefiles, aerial photography,
etc., all of which you want to integrate into your digital repository? In this
workshop, we will discuss how Hydra can provide discovery, delivery, and
management services for geospatial assets, as well as solicit questions about
your own GIS projects. We aim to help answer the following questions you might have about putting geospatial data into your Hydra-based digital library:

* What are the types of geospatial data?
* How to dive into Hydra?
* How to model geospatial holdings with Hydra?
* How to discover and view geospatial data?
* How to build a geospatial data infrastructure?
* What are common approaches and problems?

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Esmé Cowles
----

===Technology, Librarianship, and Gender: Moving the conversation forward===
'''Full Day'''

Contact: Lisa Rabey lisa @ biblyotheke dot net | [http://twitter.com/pnkrcklibrarian @pnkrcklibrarian]

'''Description'''

Librarianship is largely made up of women, yet women are significantly underrepresented in tech positions, on any level, within libraries themselves. Why? What are we doing to encourage women to become more involved in STEM within librarianship? What kind of message are we sending when library technology keynotes remain almost resolutely male? How are we changing the face of technology, not only within libraries, but with the field itself? How are we training our staff and colleagues in the areas of fairness and removal of bias? Our vendors?

Lots of tough questions.

While the conversation has been going on via various blogs and articles within the last few years, it was given a public face at [http://infotoday.com/il2013/day.asp?day=Monday#session_D105 Internet Librarian 2013] where a panel of 7 (four women, three men) gave personal experiences on the above and then opened up the conversation to the audience. As eye opening and enriching the conversation was, a 45 minute panel was not enough. One thing remains clear: We need to keep the conversation moving forward and start making some radical changes in the way we think, act, and how we need to harness this to start making real changes within librarianship itself.

Topics to include: Fairness, bias, impostor syndrome, code of conducts, sexual harassment, training opportunities, support systems, mentoring, ally support, and more

Those attending should expect: Begin with opening up the conversation of experiences and talking about what is most needed, spending remaining time putting together live, usable solutions to start implementing as well as pushing the conversation forward at local levels

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

=====All Day=====
1. Kate Kosturski

2. Valerie Aurora

3. Declan Fleming (I'd be good with a half day too)

4. mx matienzo (likewise ok w/ half day)

=====Morning=====
1. Shaun Ellis

2. Jason Casden

3. Bohyun Kim

=====Afternoon=====
1. Ayla Stein

2. Heidi Dowding

3. Coral Sheldon-Hess

4. Cory Lown
----

===FileAnalyzer: Rapid Development of File Manipulation Tasks===
'''"Half-Day" [morning]'''
* Contact Terry Brady, twb27@georgetown.edu

The FileAnalyzer (https://github.com/Georgetown-University-Libraries/File-Analyzer) is an application designed to solve a number of library automation challenges:

* validating digitized and reformatted files
* validating vendor statistics for counter compliance
* preparing collections of digital files for archiving and ingest
* manipulating ILS import and export files

The File Analyzer application was used by the US National Archives to validate 3.5 million digitized images from the 1940 Census. After implementing a customized ingest workflow within the File Analyzer, the Georgetown University Libraries was able to process an ingest backlog of over a thousand files of digital resources into DigitalGeorgetown, the Libraries’ Digital Collections and Institutional Repository platform. Georgetown is currently developing customized workflows that integrate Apache Tika, BagIt, and Marc conversion utilities.

The File Analyzer is a desktop application with a powerful framework for implementing customized file validation and transformation rules. As new rules are deployed, they are presented to users within a user interface that is easy (and powerful) to use.

The first half of this session will be targeted to potential users and developers. The second half of the session will be targeted towards developers who are interested in developing custom rules for the application.

''Session Overview''
* Overview of the application
* Running sample file tests/transformations through the application
* Compiling and building the application
* Coding a custom file processing task

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

#Ray Schwartz
# Michael Doran
----

===Collecting social media data with Social Feed Manager===
'''Half-Day [Morning]'''

Contacts:
* Dan Chudnov, GW Libraries, dchud (at) gwu.edu
* Dan Kerchner, GW Libraries, kerchner (at) gwu.edu
* Laura Wrubel, GW Libraries, lwrubel (at) gwu.edu

Social media data is a popular material for research and a new format for building collections. What does it take to collect meaningfully from Twitter, Tumblr, YouTube, Weibo, Facebook, and other sites? We will:
* Introduce options for collections, including both high- and low-end commercial offerings. Discuss what it means to collect these resources, covering boundaries, policies, and workflows required to develop a social media collection program in your institution.
* Explore the Twitter API in depth, with hands-on opportunities for those w/laptops and others who want to team up w/them
* Help you get started using the free [http://gwu-libraries.github.io/social-feed-manager Social Feed Manager] (SFM) app we're developing at GW to create your first collections. We’ll demo its use and demo a clean install (those w/environments can follow along)

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Declan Fleming
# Esmé Cowles
# Jason Stirnaman
# Ray Schwartz
# Liz Milewicz
# Ranti Junus

----

=== Intro to Git ===
'''"Half-Day [tbd - probably afternoon]"'''
* Contact: Erin Fahy, Stanford University, efahy at stanford.edu
* TA: Michael Klein, Northwestern University, michael.klein at northwestern.edu

This session will cover the fundamentals of git by discussing/going through (time allowing):
* what is a distributed version control system
* what is git and github
* initializing a repo on a remote server/github
* cloning an existing repo
* creating a branch
* contributing code to a repo
* how to handle merge conflicts

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

# Ray Schwartz
# Sam Kome
# Paula Gray-Overtoom
# Liz Milewicz
# Michael Doran
# Caitlin Christian-Lamb
# [[User:RileyChilds|Riley Childs]]
----

=== Archival discovery and use ===
'''Full Day'''

Contacts:
* Tim Shearer, UNC Chapel Hill, tshearer at email.unc.edu,
* Will Sexton, Duke, will.sexton at duke.edu

This is a full day pre-conference about archival collections and will cover the intersections of archives, workflows, technologies, discovery, and use.

Morning agenda: focused talks around (but not limited to) issues such as:
* Crowd-sourcing description to enhance collecitons
* Linked data and authority
* Mass digitization and sustainable workflows
* Digitized objects in context (images and other objects in finding aids)
* Too many cooks in the kitchen: versioning
* Global-, intra-, and inter- discovery of archival materials via finding aids
* and more...

Afternoon agenda: Focused talks around specific tools followed by general discussion, connections, opportunities, aspirations, and planning.

Tool examples:
* Archivespace
* STEADy
* "RAMP" (Remixing Archival Metadata Project)
* OpenRefine
* Aeon

''Interested in Attending''

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here

Morning:
* Julia Bauder

Afternoon:
* your name

All day:

# Josh Wilson
# Sam Kome
# Linda Ballinger
# Caitlin Christian-Lamb
# Laurie Lee Moses (seriously hard to decide here!)
# David Bass
----

===AV Content Slam===
'''Half-Day [morning]'''
Contacts:
* Kara Van Malssen, kara (at) avpreserve.com
* Lauren Sorenson, laurens (at) bavc.org
* Steven Villereal , villereal (at) gmail.com
A morning BarCamp/unconference for practitioners and coders who work with audiovisual content. The agenda will be attendee-driven, with a focus on sharing, synthesizing, and improving workflow strategies and documentation for software-based approaches to wrangling and providing access to audio and video content.
Possible topics of discussion might include:
* Use of format id and characterization/metadata extraction tools for AV
* Creating and using time-based metadata
* Managing (moving, fixity checking, etc) massive files (like uncompressed video)
For a better idea of the topics and concerns that have informed some past AV-themed events, check out the event wikis for [http://wiki.curatecamp.org/index.php/CURATEcamp_AVpres_2013 CURATEcamp AVpres 2013] as well as the [http://wiki.curatecamp.org/index.php/Association_of_Moving_Image_Archivists_%26_Digital_Library_Federation_Hack_Day_2013 AMIA/DLF 2013 Hack Day] .

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:

# A. Soroka

----

===OCLC Web Services Hackfest===

"Half-Day" [afternoon]

Contact: Shelley Hostetler, Community Manager, Developer Network hostetls[at]oclc.org

This half-day hackfest will explore some of the OCLC Developer Network web services. We will provide an overview of some of the common topics such as the general REST-based architecture for most services and how to use some new authentication clients. The group can then decide to take a deep dive into a particular API and/or write a client library for the community.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:

----

===Obey the Testing Goat!: Test Driven Web Development From The Ground Up===
'''Half-Day [tbd - probably afternoon]'''
* Contact [[User:Mredar|Mark Redar]], mredar[at]gmail.com

Test driven development is a proven method for producing better quality code. But I've found it hard to follow a strict TDD methodology when starting new web projects. How do you write that first test when there is no code or web pages created yet.

In this session, we will follow the excellent book [http://shop.oreilly.com/product/0636920029533.do "Test-Driven Web Development with Python"] to create a simple web site in Django following TDD from the first character typed. Come ready to code and test. No prior knowledge of python or Django required.

By the end of this session, you should be able to [http://www.obeythetestinggoat.com/ "Obey the Testing Goat"] from the start to finish for your next project.

If you would be interested in attending, please indicate by adding your name (but not email address, etc.) here:

# Charlie Morris (NCSU)
# Jason Stirnaman
# Joshua Gomez
# Liz Milewicz
# Scott Hanrath
# Mike Beccaria
# Sean Aery
# Carolina Garcia
----

===Summon Hackfest and ProQuest Discovery & Management Technologies Users Group ===

Presenter: Eddie Newwirth and presenters from Summon libraries
Contact: Scott Schuetze (first DOT last @ serialssolutions. com)

The morning hackfest (10:30am-12pm) will be a great opportunity for libraries using the Summon service to share their creative customizations and code and exchange ideas about ways they can leverage the Summon API to better meet the needs of their users.

The ProQuest Discovery & Management Technologies User Group (1pm-4pm) will feature updates from product managers, presentations by several libraries sharing different aspects of their experiences with ProQuest discovery and management services, and an interactive session designed to let you share your stories and discuss ideas.

The Summon Hackfest and User Group are open to all libraries currently using ProQuest discovery and management services (Intota, Summon, Ulrich’s or the 360 suite of services), whether they are attending Code4Lib or are just in the area.

----

[[:Category:Code4Lib2014]]

2014 Prepared Talk Proposals

2013-10-28T22:23:37Z

Dbs: Add Dan's structured data proposal

==2014 Prepared Talk Proposals==

'''Proposals for Prepared Talks:'''

Prepared talks are 20 minutes (including setup and questions), and should focus on one or more of the following areas:

* ''Projects'' you've worked on which incorporate innovative implementation of existing technologies and/or development of new software
* ''Tools and technologies'' – How to get the most out of existing tools, standards and protocols (and ideas on how to make them better)
* ''Technical issues'' - Big issues in library technology that should be addressed or better understood
* ''Relevant non-technical issues'' – Concerns of interest to the Code4Lib community which are not strictly technical in nature, e.g. collaboration, diversity, organizational challenges, etc.

'''To Propose a Talk'''
* Log in to the wiki in order to submit a proposal. If you are not already registered, follow the instructions to do so.
* Provide a title and brief (500 words or fewer) description of your proposed talk.
* If you so choose, you may also indicate when, if ever, you have presented at a prior Code4Lib conference. This information is completely optional, but it may assist us in opening the conference to new presenters.

As in past years, the Code4Lib community will vote on proposals that they would like to see included in the program. This year, however, only the top 10 proposals will be guaranteed a slot at the conference. Additional presentations will be selected by the Program Committee in an effort to ensure diversity in program content. Community votes will, of course, still weigh heavily in these decisions.

Presenters whose proposals are selected for inclusion in the program will be guaranteed an opportunity to register for the conference. The standard conference registration fee will still apply.

''Proposals can be submitted through '''Friday, November 8, 2013, at 5pm PST'''''. Voting will commence on November 18, 2013 and continue through December 6, 2013. The final line-up of presentations will be announced in early January, 2014.

'''Talk Proposals'''

----

== Using Drupal to drive alternative presentation systems ==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Recently, we have been building systems that use angular.js, Rails, or other systems for presentation, while leveraging Drupal's sophisticated content management capabilities on the back end.

So far, these have been one-way systems, but as we move to Drupal 8 we are beginning to explore ways to further decouple the presentation and CMS functions.

----

----
== A Book, a Web Browser and a Tablet: How Bibliotheca Alexandrina's Book Viewer Framework Makes It Possible ==

* [[User:Mohammed.abuouda|Mohammed Abu ouda]], Bibliotheca Alexandrina (The new Library of Alexandria)

A lot of institutions around the world are engaged in multiple digitization projects aiming at preserving the human knowledge present in books and availing them through multiple channels to people around the whole globe. These efforts will sure help close the digital gap particularly with the arrival of affordable e-readers, mobile phones and network coverage. However, the digital reading experience has not yet arrived to its maximum potential. Many readers miss features they like in their good old books and wish to find them in their digital counterpart. In an attempt to create a unique digital reading experience, Bibliotheca Alexandria (BA) created a flexible book viewing framework that is currently used to access its current collection of more than 300,000 digital books in five different languages which includes the largest collection of digitized Arabic books.

Using open source tools, BA used the framework to develop a modular book viewer that can be deployed in different environments and is currently at the heart of various BA projects. The Book viewer provides several features creating a more natural reading experience. As with physical books, the reader can now personalize the books he reads by adding annotations like highlights, underlines and sticky notes to capture his thoughts and ideas in addition to being able to share the book with friends on social networks. The reader can perform a search across the content of the book receiving highlighted search results within the pages of the book. More features can be further added to the book viewer through its plugin architecture.
----

== Structured data NOW: seeding schema.org in library systems ==

* [http://coffeecode.net Dan Scott], Laurentian University
** Previous code4lib presentations: [https://archive.org/details/code4lib.conf.2008.pres.CouchDBsacrilege CouchDB is sacrilege... mmm, delicious sacrilege] at Code4Lib 2008

The semantic web, linked data, and structured data are all fantastic ideas with a barrier imposed by implementation constraints. If their system does not allow customizations, or the institution lacks skilled human resources, it does not matter how enthused a given library might be about publishing structured data... it will not happen. However, if the software in use simply publishes structured data by default, then the web will be populated for free. Really! No extra resources necessary.

This presentation highlights Dan's work with systems such as Evergreen, Koha, and VuFind to enable the publication of schema.org structured data out-of-the-box. Along the way, we reflect the current state of the W3C Schema.org Bibliographic Extension community group efforts to shape the evolution of the schema.org vocabulary. Finally, hold on tight as we contemplate next steps and the possibilities of a world where structured data is the norm on the web.

----

[[:Category:Code4Lib2014]]

2013 talks proposals

2012-11-08T16:30:04Z

Dbs: Add an *AMAZING* PostgreSQL / recommendation engine talk

'''Deadline has been extended by request due to the hurricane/storm.'''

Deadline for talk submission is ''Friday, November 9'' at 11:59pm ET. We ask that no changes be made after this point, so that every voter reads the same thing. You can update your description again after voting closes.

Prepared talks are 20 minutes (including setup and questions), and focus on one or more of the following areas:
* tools (some cool new software, software library or integration platform)
* specs (how to get the most out of some protocols, or proposals for new ones)
* challenges (one or more big problems we should collectively address)

The community will vote on proposals using the criteria of:
* usefulness
* newness
* geekiness
* uniqueness
* awesomeness

Please follow the formatting guidelines:

<pre>
== Talk Title ==

* Speaker's name, affiliation, and email address
* Second speaker's name, affiliation, email address, if applicable

Abstract of no more than 500 words.
</pre>

== All Teh Metadatas Re-Revisited ==

* Esme Cowles, UC San Diego Library, escowles AT ucsd DOT edu
* Matt Critchlow, UC San Diego Library, mcritchlow AT ucsd DOT edu
* Bradley Westbrook, UC San Diego Library, bdwestbrook AT ucsd DOT edu

Last year Declan Fleming presented ALL TEH METADATAS and reviewed our UC
San Diego Library Digital Asset Management system and RDF data model. You
may be shocked to hear that all that metadata wasn't quite enough to
handle increasingly complex digital library and research data in an
elegant way. Our ad-hoc, 8-year-old data model has also been added to in
inconsistent ways and our librarians and developers have not always been
perfectly in sync in understanding how the data model has evolved over
time.

In this presentation we'll review our process of locking a team of
librarians and developers in a room to figure out a new data model, from
domain definition through building and testing an OWL ontology. We¹ll also
cover the challenges we ran into, including the review of existing
controlled vocabularies and ontologies, or lack thereof, and the decisions
made to cover the gaps. Finally, we'll discuss how we engaged the digital
library community for feedback and what we have to do next. We all know
that Things Fall Apart, this is our attempt at Doing Better This Time.

== Modernizing VuFind with Zend Framework 2 ==

* Demian Katz, Villanova University, demian DOT katz AT villanova DOT edu

When setting goals for a new major release of VuFind, use of an existing web framework was an important decision to encourage standardization and avoid reinvention of the wheel. Zend Framework 2 was selected as providing the best balance between the cutting-edge (ZF2 was released in 2012) and stability (ZF1 has a long history and many adopters). This talk will examine some of the architecture and features of the new framework and discuss how it has been used to improve the VuFind project.

== Did You Really Say That Out Loud? Tools and Techniques for Safe Public WiFi Computing ==

* [[User:DataGazetteer|Peter Murray]], LYRASIS, Peter.Murray@lyrasis.org

Public WiFi networks, even those that have passwords, are nothing more that an old-time [https://en.wikipedia.org/wiki/Party_line_(telephony) party line]: what every you say can be easily heard by anyone nearby.
Remember [https://en.wikipedia.org/wiki/Firesheep Firesheep]?
It was an extension to Firefox that demonstrated how easy it was to snag session cookies and impersonate someone else.
So what are you sending out over the airwaves, and what techniques are available to prevent eavesdropping?
This talk will demonstrate tools and techniques for desktop and mobile operating systems that you should be using right now -- right here at Code4Lib -- to protect your data and your network activity.

== Drupal 8 Preview — Symfony and Twig ==

* [[User:Highermath|Cary Gordon]], The Cherry Hill Company, cgordon@chillco.com

Drupal is a great platform for building web applications. Last year, the core developers decided to adopt the Symfony PHP framework, because it would lay the groundwork for the modernization (and de-PHP4ification) of the Drupal codebase. As I write this, the Symfony ClassLoader and HttpFoundation libraries are committed to Drupal core, with more elements likely before Drupal 8 code freeze.

It seems almost certain that the Twig templating engine will supplant PHPtemplate as the core Drupal template engine. Twig is a powerful, secure theme building tool that removes PHP from the templating system, the result being a very concise and powerful theme layer.

Symfony and Twig have a common creator, Fabien Potencier, who's overall goal is to rid the world of the excesses of PHP 4.

== Neat! But How Do We Do It? - The Real-world Problem of Digitizing Complex Corporate Digital Objects ==

* Matthew Mariner, University of Colorado Denver, Auraria Library, matthew.mariner@ucdenver.edu

Isn't it neat when you discover that you are the steward of dozens of Sanborn Fire Instance Maps, hundreds of issues of a city directory, and thousands of photographs of persons in either aforementioned medium? And it's even cooler when you decide, "Let's digitize these together and make them one big awesome project to support public urban history"? Unfortunately it's a far more difficult process than one imagines at inception and, sadly, doesn't always come to fruition. My goal here is to discuss the technological (and philosophical) problems librarians and archivists face when trying to create ultra-rich complex corporate digital projects, or, rather, projects consisting of at least three facets interrelated by theme. I intend to address these problems by suggesting management solutions, web workarounds, and, perhaps, a philosophy that might help in determining whether to even move forward or not. Expect a few case studies of "grand ideas crushed by technological limitations" and "projects on the right track" to follow.

== ResCarta Tools building a standard format for audio archiving, discovery and display ==

* [[User:sarney|John Sarnowski]], The ResCarta Foundation, john.sarnowski@rescarta.org

The free ResCarta Toolkit has been used by libraries and archives around the world to host city directories, newspapers, and historic photographs and by aerospace companies to search and find millions of engineering documents. Now the ResCarta team has released audio additions to the toolkit.

Create full text searchable oral histories, news stories, interviews. or build an archive of lectures; all done to Library of Congress standards. The included transcription editor allows for accurate correction of the data conversion tool’s output. Build true archives of text, photos and audio. A single audio file carries the embedded Axml metadata, transcription, and word location information. Checks with the FADGI BWF Metaedit.

ResCarta-Web presents your audio to IE, Chome, Firefox, Safari, and Opera browsers with full playback and word search capability. Display format is OGG!!

You have to see this tool in action. Twenty minutes from an audio file to transcribed, text-searchable website. Be there or be L seven (Yeah, I’m that old)

== Format Designation in MARC Records: A Trip Down the Rabbit-Hole ==

* Michael Doran, University of Texas at Arlington, doran@uta.edu

This presentation will use a seemingly simple data point, the "format" of the item being described, to illustrate some of the complexities and challenges inherent in the parsing of MARC records. I will talk about abstract vs. concrete forms; format designation in the Leader, 006, 007, and 008 fixed fields as well as the 245 and 300 variable fields; pseudo-formats; what is mandatory vs. optional in respect to format designation in cataloging practice; and the differences between cataloging theory and practice as observed via format-related data mining of a mid-size academic library collection.

I understand that most of us go to code4lib to hear about the latest sexy technologies. While MARC isn't sexy, many of the new tools being discussed still need to be populated with data gleaned from MARC records. MARC format designation has ramifications for search and retrieval, limits, and facets, both in the ILS and further downstream in next generation OPACs and web-scale discovery tools. Even veteran library coders will learn something from this session.

== Touch Kiosk 2: Piezoelectric Boogaloo ==

* Andreas Orphanides, North Carolina State University Libraries, akorphan@ncsu.edu

At the NCSU Libraries, we provide realtime access to information on library spaces and services through an interactive touchscreen kiosk in our Learning Commons. In the summer of 2012, two years after its initial deployment, I redeveloped the kiosk application from the ground up, with an entirely new codebase and a completely redesigned user interface. The changes I implemented were designed to remedy previously identified shortcomings in the code and the interface design [1], and to enhance overall stability and performance of the application.

In this presentation I will outline my revision process, highlighting the lessons I learned and the practices I implemented in the course of redevelopment. I will highlight the key features of the HTML/Javascript codebase that allow for increased stability, flexibility, and ease of maintenance; and identify the changes to the user interface that resulted from the usability findings I uncovered in my previous research. Finally, I will compare the usage patterns of the new interface to the analysis of the previous implementation to examine the practical effect of the implemented changes.

I will also provide access to a genericized version of the interface code for others to build their own implementations of similar kiosk applications.

[1] http://journal.code4lib.org/articles/5832

== Wayfinding in a Cloud: Location Service for libraries ==

* Petteri Kivimäki, The National Library of Finland, petteri.kivimaki@helsinki.fi

Searching for books in large libraries can be a difficult task for a novice library user. This paper presents The Location Service, software as a service (SaaS) wayfinding application developed and managed by The National Library of Finland, which is targeted for all the libraries. The service provides additional information and map-based guidance to books and collections by showing their location on a map, and it can be integrated with any library management system, as the integration happens by adding a link to the service in the search interface. The service is being developed continuously based on the feedback received from the users.

The service has two user interfaces: One for the customers and one for the library staff for managing the information related to the locations. The UI for the customers is fully customizable by the libraries, and the customization is done via template files by using the following techniques: HTML, CSS, and Javascript/jQuery. The service supports multiple languages, and the libraries have a full control of the languages, which they want to support in their environment.

The service is written in Java and it uses Spring and Hibernate frameworks. The data is stored in PostgreSQL database, which is shared by all the libraries. They do not possess a direct access to the database, but the service offers an interface, which makes it possible to retrieve XML data over HTTP. Modification of the data via admin UI, however, is restricted, and access on the other libraries’ data is blocked.

== Empowering Collection Owners with Automated Bulk Ingest Tools for DSpace ==

* Terry Brady, Georgetown University, twb27@georgetown.edu

The Georgetown University Library has developed a number of applications to expedite the process of ingesting content into DSpace.
* Automatically inventory a collection of documents or images to be uploaded
* Generate a spreadsheet for metadata capture based on the inventory
* Generate item-level ingest folders, contents files and dublin core metadata for the items to be ingested
* Validate the contents of ingest folders prior to initiating the ingest to DSpace
* Present users with a simple, web-based form to initiate the batch ingest process

The applications have eliminated a number of error-prone steps from the ingest workflow and have significantly reduced a number of tedious data editing steps. These applications have empowered content experts to be in charge of their own collections.

In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.

== Quality Assurance Reports for DSpace Collections ==

* Terry Brady, Georgetown University, twb27@georgetown.edu

The Georgetown University Library has developed a collection of quality assurance reports to improve the consistency of the metadata in our DSpace collections. The report infrastructure permits the creation of query snippets to test for possible consistency errors within the repository such as items missing thumbnails, items with multiple thumbnails, items missing a creation date, items containing improperly formatted dates, items without duplicated metadata fields, items recently added items across the repository, a community or a collection

These reports have served to prioritize programmatic data cleanup tasks and manual data cleanup tasks. The reports have served as a progress tracker for data cleanup work and will provide on-going monitoring of the metadata consistency of the repository.

In this presentation, I will provide a demonstration of the tools that were built and discuss the development process that was followed.

== A Hybrid Solution for Improving Single Sign-On to a Proxy Service with Squid and EZproxy through Shibboleth and ExLibris’ Aleph X-Server ==

* Alexander Jerabek, UQAM - Université du Québec à Montréal, jerabek.alexander_j@uqam.ca
* Minh-Quang Nguyen, UQAM - Université du Québec à Montréal, nguyen.minh-quang@uqam.ca

In this talk, we will describe how we developed and implemented a hybrid solution for improving single sign-on in conjunction with the library’s proxy service. This hybrid solution consists of integrating the disparate elements of EZproxy, the Squid workflow, Shibboleth, and the Aleph X-Server. We will report how this new integrated service improves the user experience. To our knowledge, this new service is unique and has not been implemented anywhere else. We will also present some statistics after approximately one year in production.

See article: http://journal.code4lib.org/articles/7470

== HTML5 Video Now! ==

* Jason Ronallo, North Carolina State University Libraries, jnronall@ncsu.edu

Can you use HTML5 video now? Yes.

I'll show you how to get started using HTML5 video, including gotchas, tips, and tricks. Beyond the basics we'll see the power of having video integrated into HTML and the browser. Finally, we'll look at examples that push the limits and show the exciting future of video on the Web.

My experience comes from technical development of an oral history video clips project. I developed the technical aspects of the project, including video processing, server configuration, development of a public site, creation of an administrative interface, and video engagement analytics. Major portions of this work have been open sourced under an MIT license.

== Hybrid Archival Collections Using Blacklight and Hydra ==

* Adam Wead, Rock and Roll Hall of Fame and Museum, awead@rockhall.org

At the Library and Archives of the Rock and Roll Hall of Fame, we use available tools such as Archivists' Toolkit to create EAD finding aids of our collections. However, managing digital content created from these materials and the born-digital content that is also part of these collections represents a significant challenge. In my presentation, I will discuss how we solve the problem of our hybrid collections by using Hydra as a digital asset manager and Blacklight as a unified presentation and discovery interface for all our materials.

Our strategy centers around indexing ead xml into Solr as multiple documents: one for each collection, and one for every series, sub-series and item contained within a collection. For discovery, we use this strategy to leverage item-level searching of archival collections alongside our traditional library content. For digital collections, we use this same technique to represent a finding aid in Hydra as a set of linked objects using RDF. New digital items are then linked to these parent objects at the collection and series level. Once this is done, the items can be exported back out to the Blacklight solr index and the digital content appears along with the rest of the items in the collection.

== Making the Web Accessible through Solid Design ==

* [[User:Cynthia|Cynthia Ng]] from Ryerson University Library & Archives

In libraries, we are always trying our best to be accessible to everyone and we make every effort to do so physically, but what about our websites? Web designers are great at talking about the user experience and how to improve it, but what sometimes gets overlooked is how to make a site more accessible and meet accessibility guidelines. While guidelines are necessary to cover a minimum standard, web accessibility should come from good web design without ‘sacrificing’ features. While it's difficult to make a website fully accessible to everyone, there are easy, practical ways to make a site as accessible as possible.

While the focus will be on websites and meeting the Web Accessibility Guidelines WCAG, the presentation will also touch on how to make custom web interfaces accessible.

== Getting People to What They Need Fast! A Wayfinding Tool to Locate Books & Much More ==

* Steven Marsden, Ryerson University Library & Archives, steven dot marsden at ryerson dot ca
* [[User:Cynthia|Cynthia Ng]], Ryerson University Library & Archives

Having a bewildered, lost user in the building or stacks is a common occurrence, but we can help our users find their way through enhanced maps and floor plans. While not a new concept, these maps are integrated into the user’s flow of information without having to load a special app. The map not only highlights the location, but also provides all the related information with a link back to the detailed item view. During the first stage of the project, it has only be implemented for books (and other physical items), but the 'RULA Finder' is built to help users find just about anything and everything in the library including study rooms, computer labs, and staff. With a simple to use admin interface, it makes it easy for everyone, staff and users.

The application is written in PHP with data stored in a MySQL database. The end-user interface involves jQuery, JSON, and the library's discovery layer (Summon) API.

The presentation will not only cover the technical aspects, but also the implementation and usability findings.

== De-sucking the Library User Experience ==

* Jeremy Prevost, Northwestern University, j-prevost {AT} northwestern [DOT] edu

Have you ever thought that library vendors purposely create the worst possible user experience they can imagine because they just hate users? Have you ever thought that your own library website feels like it was created by committee rather than for users because, well, it was? I’ll talk about how we used vendor supplied APIs to our ILS and Discovery tool to create an experience for our users that sucks at least a little bit less.

The talk will provide specific examples of how inefficient or confusing vendor supplied solutions are from a user perspective along with our specific streamlined solutions to the same problems. Code examples will be minimal as the focus will be on improving user experience rather than any one code solution of doing that. Examples may include the seemingly simple tasks of renewing a book or requesting an item from another campus library.

== Solr Testing Is Easy with Rspec-Solr Gem ==

* Naomi Dushay, Stanford University, ndushay AT stanford DOT edu

How do you know if

* your idea for "left anchoring" searches actually works?
* your field analysis for LC call numbers accommodates a suffix between the first and second cutter without breaking the rest of LC call number parsing?
* tweaking Solr configs to improve, say, Chinese searching, won't break Turkish and Cyrillic?
* changes to your solrconfig file accomplish what you wanted without breaking anything else?

Avoid the whole app stack when writing Solr acceptance/relevancy/regression tests! Forget cucumber and capybara. This gem lets you easily (only 4 short files needed!) write tests like this, passing arbitrary parameters to Solr:

it "unstemmed author name Zare should precede stemmed variants" do
resp = solr_response(author_search_args('Zare').merge({'fl'=>'id,author_person_display', 'facet'=>false}))
resp.should include("author_person_display" => /\bZare\W/).in_each_of_first(3).documents
resp.should_not include("author_person_display" => /Zaring/).in_each_of_first(20).documents
end

it "Cyrillic searching should work: Восемьсoт семьдесят один день" do
   resp = solr_resp_doc_ids_only({'q'=>'Восемьсoт семьдесят один день'})
   resp.should include("9091779")
end

it "q of 'String quartets Parts' and variants should be plausible " do
   resp = solr_resp_doc_ids_only({'q'=>'String quartets Parts'})
   resp.should have_at_least(2000).documents
   resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=>'(String quartets Parts)'}))
   resp.should have_more_results_than(solr_resp_doc_ids_only({'q'=>'"String quartets Parts"'}))
end

it "Traditional Chinese chars 三國誌 should get the same results as simplified chars 三国志" do
resp = solr_response({'q'=>'三國誌', 'fl'=>'id', 'facet'=>false})
resp.should have_at_least(240).documents
resp.should have_the_same_number_of_results_as(solr_resp_doc_ids_only({'q'=>'三国志'}))
end

See
http://rubydoc.info/github/sul-dlss/rspec-solr/frames
https://github.com/sul-dlss/rspec-solr

and our production relevancy/acceptance/regression tests slowly migrating from cucumber to:
https://github.com/sul-dlss/sw_index_tests

== Northwestern's Digital Image Library ==

*Mike Stroming, Northwestern University Library, m-stroming AT northwestern DOT edu
*Edgar Garcia, Northwestern University Library, edgar-garcia AT northwestern DOT edu

At Northwestern University Library, we are about to release a beta version of our Digital Image Library (DIL). DIL is an implementation of the Hydra technology that provides a Fedora repository solution for discovery of and access to over 100,000 images for staff, students, and scholars. Some important features are:

*Build custom collection of images using drag-and-drop
*Re-order images within a collection using drag-and-drop
*Nest collections within other collections
*Create details/crops of images
*Zoom, rotate images
*Upload personal images
*Retrieve your own uploads and details from a collection
*Export a collection to a PowerPoint presentation
*Create a group of users and authorize access to your images
*Batch edit image metadata

Our presentation will include a demo, explanation of the architecture, and a discussion of the benefits of being a part of the Hydra open-source community.

== Two standards in a software (to say nothing of Normarc) ==

*Zeno Tajoli, CINECA (Italy), z DOT tajoli AT cineca DOT it

With this presentation I want to show how ILS Koha handles the support of three differnt MARC dialects:
MARC21, Unimarc and Normarc. The main points of the presentation:

*Three MARC at MySQL level
*Three MARC at API level
*Three MARC at display
*Can I add a new format ?

== Future Friendly Web Design for Libraries ==

*[[User:michaelschofield|Michael Schofield]], Alvin Sherman Library, Research, and Information Technology Center, mschofied[dot]nova[dot]edu

Libraries on the web are afterthoughts. Often their design is stymied on one hand by red tape imposed by the larger institution and on the other by an overload of too democratic input from colleagues. Slashed budgets / staff stretched too thin foul-up the R-word (that'd be "redesign") - but things are getting pretty strange. Notions about the Web (and where it can be accessed) are changing.

So libraries can only avoid refabbing their fixed-width desktop and jQuery Mobile m-dot websites for so long until desktop users evaporate and demand from patrons with web-ready refrigerators becomes deafening. Just when we have largely hopped on the bandwagon and gotten enthusiastic about being online, our users expect a library's site to look and perform great on everything.

Our presence on the web should be built to weather ever-increasing device complexity. To meet users at their point of need, libraries must start thinking Future Friendly.

This overview rehashes the approach and philosophy of library web design, re-orienting it for maximum accessibility and maximum efficiency of design. While just 20 minutes, we'll mull over techniques like mobile-first responsive web design, modular CSS, browser feature detection for progressive enhancement, and lots of nifty tricks.

==BYU's discovery layer service aggregator==

*Curtis Thacker, Brigham Young University, curtis.thacker AT byu DOT edu

It is clear that libraries will continue to experience rapid change based on the speed of technology. To acknowledge this new reality and to provide rapid response to shifting end user paradigms BYU has developed a custom service aggregator. At first our vendors looked at us a bit funny; however, in the last year they have been astonished with the fluid implementation of new services – here’s the short list:

*filmfinder - a tool for browsing and searching films
*A custom book recommender service based on checkout data
*Integrated library services like personell, library hours, study room scheduler and database finder through a custom adwords system.
*A very geeky and powerful utility used for converting marc XML into primo compliant xml.
*Embedded floormaps
*A responsive web design
*Bing did-you-mean
*And many more.

I will demo the system, review the archtecture and talk about future plans.

==The Avalon Media System: A Next Generation Hydra Head For Audio and Video Delivery==

* Michael Klein, Senior Software Developer, Northwestern University LIbrary, michael.klein AT northwestern DOT edu
* Nathan Rogers, Programmer/Analyst, Indiana University, rogersna AT indiana DOT edu

Based on the success of the [http://www.dml.indiana.edu/ Variations] digital music platform, Indiana University and Northwestern University have developed a next generation educational tool for delivering multimedia resources to the classroom. The Avalon Media System (formerly Variations on Video) supports the ingest, media processing, management, and access-controlled delivery of library-managed video and audio collections. To do so, the system draws on several existing, mature, open source technologies:

* The ingest, search, and discovery functionality of the Hydra framework
* The powerful multimedia workflow management features of Opencast Matterhorn
* The flexible Engage audio/video player
* The streaming capabilities of both Red5 Media Server (open source) and Adobe Flash Media Server (proprietary)

Extensive customization options are built into the framework for tailoring the application to the needs of a specific institution.

Our goal is to create an open platform that can be used by other institutions to serve the needs of the academic community. Release 1 is planned for a late February launch with future versions released every couple of months following. For more information visit http://avalonmediasystem.org/ and https://github.com/variations-on-video/hydrant.

== The DH Curation Guide: Building a Community Resource ==

*Robin Davis, John Jay College of Criminal Justice, robdavis AT jjay.cuny.edu
*James Little, University of Illinois Urbana-Champaign, little9 AT illinois.edu

Data curation for the digital humanities is an emerging area of research and practice. The DH Curation Guide, launched in July 2012, is an educational resource that addresses aspects of humanities data curation in a series of expert-written articles. Each provides a succinct introduction to a topic with annotated lists of useful tools, projects, standards, and good examples of data curation done right. The DH Curation Guide is intended to be a go-to resource for data curation practitioners and learners in libraries, archives, museums, and academic institutions.

Because it's a growing field, we designed the DH Curation Guide to be a community-driven, living document. We developed a granular commenting system that encourages data curation community members to contribute remarks on articles, article sections, and article paragraphs. Moreover, we built in a way for readers to contribute and annotate resources for other data curation practitioners.

This talk will address how the DH Curation Guide is currently used and will include a sneak peek at the articles that are in store for the Guide’s future. We will talk about the difficulties and successes of launching a site that encourages community. We are all builders here, so we will also walk through developing the granular commenting/annotation system and the XSLT-powered publication workflow.

== Solr Update ==

*Erik Hatcher, LucidWorks, erik.hatcher AT lucidworks.com

Solr is continually improving. Solr 4 was recently released, bringing dramatic changes in the underlying Lucene library and Solr-level features. It's tough for us all to keep up with the various versions and capabilities.

This talk will blaze through the highlights of new features and improvements in Solr 4 (and up). Topics will include: SolrCloud, direct spell checking, surround query parser, and many other features. We will focus on the features library coders really need to know about.

== Reports for the People ==

*Kara Young, Keene State College, NH, kyoung1 at keene.edu
*Dana Clark, Keene State College, NH, dclark5 at keene.edu

Libraries are increasingly being called upon to provide information on how our programs and services are moving our institutional strategic goals forward. In support of College and departmental Information Literacy learning outcomes, Mason Library Systems at Keene State College developed an assessment database to record and report assessment activities by Library faculty. Frustrated by the lack of freely available options for intuitively recording, accounting for, and outputting useful reports on instructional activities, Librarians requested a tool to make capturing and reporting activities (and their lives) easier. Library Systems was able to respond to this need by working with librarians to identify what information is necessary to capture, where other assessment tools had fallen short, and ultimately by developing an application that supports current reporting imperatives while providing flexibility for future changes.

The result of our efforts was an in-house browser interfaced Assessment Database to improve the process of data collection and analysis. The application is written in PHP, data stored in a MySQL database, and presented via browser making extensive use of JQuery and JQuery plug-ins for data collection, manipulation, and presentation.
The presentation will outline the process undertaken to build a successful collaboration with Library faculty from conception to implementation, as well as the technical aspects of our trial-and-error approach. Plus: cool charts and graphs!

== Network Analyses of Library Catalog Data ==

* Kirk Hess, University of Illinois at Urbana-Champaign, kirkhess AT illinois.edu
* Harriett Green, University of Illinois at Urbana-Champaign, green19 AT illinois.edu

Library collections are all too often like icebergs: The amount exposed on the surface is only a fraction of the actual amount of content, and we’d like to recommend relevant items from deep within the catalog to users. With the assistance of an XSEDE Allocation grant (http://xsede.org), we’ve used R to reconstitute anonymous circulation data from the University of Illinois’s library catalog into separate user transactions. The transaction data is incorporated into subject analyses that use XSEDE supercomputing resources to generate predictive network analyses and visualizations of subject areas searched by library users using Gephi (https://gephi.org/). The test data set for developing the subject analyses consisted of approximately 38,000 items from the Literatures and Languages Library that contained 110,000 headings and 130,620 transactions. We’re currently working on developing a recommender system within VuFind to display the results of these analyses.

== Pitfall! Working with Legacy Born Digital Materials in Special Collections ==

* Donald Mennerich, The New York Public Library, don.mennerich AT gmail.com
* Mark A. Matienzo, Yale University Library, mark AT matienzo.org

Archives and special collections are being faced with a growing abundance of born digital material, as well as an abundance of many promising tools for managing them. However, one must consider the potential problems that can arise when approaching a collection containing legacy materials (from roughly the pre-internet era). Many of the tried and true, "best of breed" tools for digital preservation don't always work as they do for more recent materials, requiring a fair amount of ingenuity and use of "word of mouth tradecraft and knowledge exchanged through serendipitous contacts, backchannel conversations, and beer" (Kirschenbaum, "Breaking <code>badflag</code>").

Our presentation will focus on some of the strange problems encountered and creative solutions devised by two digital archivists in the course of preserving, processing, and providing access to collections at their institutions. We'll be placing particular particular emphasis of the pitfalls and crocodiles we've learned to swing over safely, while collecting treasure in the process. We'll address working with CP/M disks in collections of authors' papers, reconstructing a multipart hard drive backup spread across floppy disks, and more.

== Project <s>foobar</s> FUBAR ==

* Becky Yoose, Grinnell College, yoosebec AT grinnell DOT edu

Be it mandated from Those In A Higher Pay Grade Than You or self-inflicted, many of us deal with managing major library-related technology projects [1]. It’s common nowadays to manage multiple technology projects, and generally external and internal issues can be planned for to minimize project timeline shifts and quality of deliverables. Life, however, has other plans for you, and all your major library technology infrastructure projects pile on top of each other at the same time. How do you and your staff survive a train wreck of technology projects and produce deliverables to project stakeholders without having to go into the library IT version of the United States Federal Witness Protection Program?

This session covers my experience with the collision of three major library technology projects - including a new institutional repository and an integrated library system migration - and how we dealt with external and internal factors, implemented damage control, and overall lessening the damage from the epic crash. You might laugh, you might cry, you will probably have flashbacks from previous projects, but you will come out of this session with a set of tools to use when you’re dealing with managing mission-critical projects.

[1] Past code4lib talks have covered specific project management strategies, such as Agile, for application development. I will be focusing on and discussing general project management practices in relation to various library technology projects, many of which these strategies include in their own structures.

== Implementing RFID in an Academic Library ==

* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu

Coastal Carolina University’s Kimbel Library recently implemented RFID to increase security, provide better inventory control over library materials and enable do-it-yourself patron services such as self checkout.

I’ll give a quick overview of RFID and the components involved and then will talk about how our library utilized the technology. It takes a lot of research, time, money and not too little resourcefulness to make your library RFID-ready. I’ll show how we developed our project timeline, how we assessed and evaluated vendors and how we navigated the bid process. I’ll also talk about hardware and software installation, configuration and troubleshooting and will discuss our book and media collection encoding process.

We encountered myriad issues with our vendor, the hardware and the software. Would we do it all over again? Should your library consider RFID? Caveats abound...

== Coding an Academic Library Intranet in Drupal: Now We're Getting Organizized... ==

* Scott Bacon, Coastal Carolina University, sbacon AT coastal DOT edu

The Kimbel Library Intranet is coded in Drupal 7, and was created to increase staff communication and store documentation. This presentation will contain an overview of our intranet project, including the modules we used, implementation issues, and possible directions in future development phases. I won’t forget to talk about the slew of tasty development issues we faced, including dealing with our university IT department, user buy-in, site navigation, user roles, project management, training and mobile modules (or the lack thereof). And some other fun (mostly) true anecdotes will surely be shared.

The main functions of Phase I of this project were to increase communication across departments and committees, facilitate project management and revise the library's shared drive. Another important function of this first phase was to host mission-critical documentation such as strategic goals, policies and procedures. Phase II of this project will focus on porting employee tasks into the centralized intranet environment. This development phase, which aims to replicate and automate the bulk of staff workflows within a content management system, will be a huge undertaking.

We chose Drupal as our intranet platform because of its extensibility, flexibility and community support. We are also moving our entire library web presence to Drupal in 2013 and will be soliciting any advice on which modules to use/avoid and which third-party services to wrangle into the Drupal environment. Should we use Drupal as the back-end to our entire Web presence? Why or why not?

== Hands off! Best Practices and Top Ten Lists for Code Handoffs ==

* Naomi Dushay, Stanford University Library, ndushay@stanford.edu
* Bess Sadler, Stanford University Library, bess@stanford.edu

Transition points in who is the primary developer on an actively developing code base can be a source of frustration for everyone involved. We've tried to minimize that pain point as much as possible through the use of agile methods like test driven development, continuous integration, and modular design. Has optimizing for developer happiness brought us happiness? What's worked, what hasn't, and what's worth adopting? How do you keep your project in a state where you can easily hand it off?

== How to be an effective evangelist for your open source project ==

* Bess Sadler, Stanford University Library, bess@stanford.edu

The difference between an open source software project that gets new adopters and new contributing community members (which is to say, a project that goes on existing for any length of time) and a project that doesn't, often isn't a question of superior design or technology. It's more often a question of whether the advocates for the project can convince institutional leaders AND front line developers that a project is stable and trustworthy. What are successful strategies for attracting development partners? I'll try to answer that and talk about what we could do as a community to make collaboration easier.

== Thoughts from an open source vendor - What makes a "good" vendor in a meritocracy? ==

* Matt Zumwalt, Data Curation Experts / MediaShelf / Hydra Project, matt@curationexperts.com

What is the role of vendors in open source? What should be the position of vendors in a meritocracy? What are the avenues for encouraging great vendors who contribute to open source communities in valuable ways? How you answer these questions has a huge impact on a community, and in order to formulate strong answers, you need to be well informed. Let’s glimpse at the business practicalities of this situation, beginning with 1) an overview of the viable profit models for open-source software, 2) some of the realities of vendor involvement in open source, and 3) an account of the ins & outs of compensation & equity structures within for-profit corporations.

The topics of power & influence, fairness, community participation, software quality, employment and personal profit are fair game, along with software licensing, support, sponsorship, closed source software and the role of sales people.

This presentation will draw on personal experience from the past seven years spent bootstrapping and running MediaShelf, a small but prolific for-profit consulting company that focuses entirely on open source digital repository software. MediaShelf has played an active role in creating the Hydra Framework and continuously contributes to maintenance of Fedora and Blacklight. Those contributions have been funded through consulting contracts for authoring & implementing open source software on behalf of organizations around the world.

==Occam’s Reader: A system that allows the sharing of eBooks via Interlibrary Loan==

*Ryan Litsey, Texas Tech University, Ryan DOT Litsey AT ttu.edu
*Kenny Ketner, Texas Tech University, Kenny DOT Ketner AT ttu.edu

Occam’s Reader is a software platform that allows the transfer and sharing of electronic books between libraries via existing interlibrary loan software. Occam’s Reader allows libraries to meet the growing need to be able to share our electronic resources. In the ever-increasing digital world, many of our collection development plans now include eBook platforms. The problem with eBooks, however, is that they are resources that are locked into the home library. With Occam’s Reader we can continue the centuries-old tradition of resource sharing and also keep up with the changing digital landscape.

== Using Puppet for configuration management when no two servers look alike ==
* Eugene Vilensky, Senior Systems Administrator, Northwestern University Library, evilensky northwestern edu

Configuration management is hot because it allows one to scale to thousands of machines, all of which look alike, and tightly manage changes across the nodes. Infrastructure as code, implement all changes programmatically, yadda yadda yadda.

Unfortunately, servers which have gone unmanaged for a long time do not look very similar to each other. Variables come in many forms, usually because of some or all of the following: Who installed the server, where it was installed, where the image was sourced from, when it was installed, where additional packages were sourced, and what kind of software was hosted on it.

Bringing such machines into your configuration management platform is no harder and no easier than some or all of the following options options: 1) blow such machines away and start from scratch, migrate your data. 2) Find the lowest common baseline between the current state and the ideal state and start the work there. 3) implement new features/services on existing unmanaged machines but manage the new features/services.

I will describe our experiences at the library for all three options using the Puppet open-source tool on Enterprise Linux 5 and 6.

== REST <b>IS</b> Your Mobile Strategy ==

* Richard Wolf, University of Illinois at Chicago, richwolf@uic.edu

Mobile is the new hotness ... and you can't be one of the cool kids unless you've got your own mobile app ... but the road to mobility is daunting. I'll argue that it's actually easier than it seems ... and that the simplest way to mobility is to bring your data to the party, create a REST API around the data, tell developers about your API, and then let the magic happen. To make my argument concrete, I'll show (lord help me!) how to go from an interesting REST API to a fun iOS tool for librarians and the general public in twenty minutes.

== ARCHITECTING ScholarSphere: How We Built a Repository App That Doesn't Feel Like Yet Another Janky Old Repository App ==

* Dan Coughlin, Penn State University, danny@psu.edu
* Mike Giarlo, Penn State University, michael@psu.edu

ScholarSphere is a web application that allows the Penn State research community to deposit, share, and manage its scholarly works. It is also, as some of our users and our peers have observed, a repository app that feels much more like Google Docs or GitHub than earlier-generation repository applications. ScholarSphere is built upon the Hydra framework (Fedora Commons, Solr, Blacklight, Ruby on Rails), MySQL, Redis, Resque, FITS, ImageMagick, jQuery, Bootstrap, and FontAwesome. We'll talk about techniques we used to:

* eliminate Fedora-isms in the application
* model and expose RDF metadata in ways that users find unobtrusive
* manage permissions via a UI widget that doesn't stab you in the face
* harvest and connect controlled vocabularies (such as LCSH) to forms
* make URIs cool
* keep the app snappy without venturing into the architectural labyrinth of YAGNI
* build and queue background jobs
* expose social features and populate activity streams
* tie checksum verification, characterization, and version control to the UI
* let users upload and edit multiple files at once

The application will be demonstrated; code will be shown; and we solemnly commit to showing ABSOLUTELY NO XML.

==Coding with Mittens==

*Jim LeFager, DePaul University Library jlefager@depaul.edu

Working in an environment where developers have restricted access to servers and development areas, or where you are primarily working in multiple hosted systems with limited access, can be a challenge when you are attempting to incorporate any new functionality or improve an existing one. Hosted web services present a benefit so that staff time is not dedicated to server maintenance and development, but customization can be difficult and at times impossible. In many cases, incorporating any current API functionality requires additional work besides the original development work which can be frustrating and inefficient. The result can be a Frankenstein monster of web services that is confusing to the user and difficult to navigate.

This talk will focus on some effective best practices, and maybe not so great but necessary practices that we have adopted to develop and improve our user’s experience using javascript/jQuery and CSS to manipulate our hosted environments. This will include a review of available tools that allow collaborative development in the cloud, as well as examples of jQuery methods that have allowed us to take additional control of these hosted environments as well as track them using Google Analytics. Included will be examples from Springshare Campus Guides, CONTENTdm and other hosted web spaces that have been ‘hacked’ to improve the UI.

== Hacking the DPLA ==
* Nate Hill, Chattanooga Public Library, nathanielhill AT gmail.com
* Sam Klein, Wikipedia, metasj AT gmail.com

The Digital Public Library of America is a growing open-source platform to support digital libraries and archives of all kinds. DPLA-alpha is available for testing, with data from six initial Hubs. New APIs and data feeds are in development, with the next release scheduled for April.

Come learn what we are doing, how to contribute or hack the DPLA roadmap, and how you (or your favorite institution) can draw from and publish through it. Larger institutions can join as a (content or service) hub, helping to aggregate and share metadata and services from across their {region, field, archive-type}. We will discuss current challenges and possibilities (UI and API suggestions wanted!), apps being built on the platform, and related digitization efforts.

DPLA has a transparent community and planning process; new participants are always welcome. Half the time will be for suggestions and discussion. Please bring proposals, problems, partnerships and possible paradoxes to discuss.

== Introduction to SilverStripe 3.0 ==

* Ian Walls, University of Massachusetts Amherst, iwalls AT library DOT umass DOT edu

SilverStripe is an open source Content Management System/development framework out of New Zealand, written in PHP, with a solid MVC structure. This presentation will cover everything you need to know to get started with SilverStripe, including
* Features (and why you should consider SilverStripe)
* Requirements & Installation
* Model-View-Controller
* Key data types & configuration settings
* Modules
* Where to start with customization
* Community support and participation

== Citation search in SOLR and second-order operators ==

* Roman Chyla, Astrophysics Data System, roman.chyla AT (cfa.harvad.edu|gmail.com)

Citation search is basically about connections (Is the paper read by a friend of mine more important than others? Get me a paper read by somebody who cites many papers/is cited by many papers?), but the implementation of the citation search is surprisingly useful in many other areas.

I will show 'guts' of the new citation search for astrophysics, it is generic and can be applied recursively to any Lucene query. Some people would call it a second-order operation because it works with the results of the previous (search) function. The talk will see technical details of the special query class, its collectors, how to add a new search operator and how to influence relevance scores. Then you can type with me: friends_of(friends_of(cited_for(keyword:"black holes") AND keyword:"red dwarf"))

== Managing Segmented Images and Hierarchical Collections with Fedora-Commons and Solr ==

* David Lacy, Villanova University, david DOT lacy AT villanova.edu

Many of the resources within our digital library are split into parts -- newspapers, scrapbooks and journals being examples of collections of individual scanned pages. In some cases, groups of pages within a collection, or segments within a particular page, may also represent chapters or articles.

We recently devised a procedure to extract these "segmented resources" into their own objects within our repository, and index them individually in our Discovery Layer.

In this talk I will explain how we dissected and organized these newly created resources with an extension to our Fedora Model, and how we make them discoverable through Solr configurations that facilitate browsable hierarchical relationships and field-collapsed results that group items within relevant resources.

== Google Analytics, Event Tracking and Discovery Tools==

* Emily Lynema, North Carolina State University Libraries. ejlynema AT ncsu DOT edu
* Adam Constabaris, North Carolina State University Libraries, ajconsta AT ncsu DOT edu

The NCSU Libraries is using Google Analytics increasingly across its website as a replacement for usage tracking via Urchin. More recently, we have also begun to use the event tracking features in Google Analytics. This has allowed us to gather usage statistics for activities that don’t initiate new requests to the server, such as clicks that hide and show already-loaded content (as in many tabbed interfaces). Aggregating these events together with pageview tracking in Google Analytics presents a more unified picture of patron activity and can help improve design of tools like the library catalog. While assuming a basic understanding of the use of Google Analytics pageview tracking, this presentation will start with an introduction to the event tracking capabilities that may be less widely known.

We’ll share library catalog usage data pulled from Google Analytics, including information about features that are common across the newest wave of catalog interfaces, such as tabbed content, Google Preview, and shelf browse. We will also cover the approach taken for the technical implementation of this data-intensive JavaScript event tracking.

As a counterpart, we can demonstrate how we have begun to use Google Analytics event tracking in a proprietary vendor discovery tool (Serials Solutions Summon). While the same technical ideas govern this implementation, we can highlight the differences (read, challenges) inherent in utilizing this type of event tracking in vendor-owned application vs. a locally developed application.

Along the way, hopefully you’ll learn a little about why you might (or might not) want to use Google Analytics event tracking yourself and see some interesting catalog usage stats.

== Actions speak louder than words: Analyzing large-scale query logs to improve the research experience ==

* Raman Chandrasekar, Serials Solutions, Raman DOT Chandrasekar AT serialssolutions DOT com
* Ted Diamond, Serials Solutions, Ted DOT Diamond AT serialssolutions DOT com

Analyzing anonymized query and click through logs leads to a better understanding of user behaviors and intentions and provides great opportunities to respond to users with an improved search experience. A large-scale provider of SaaS services, Serials Solutions is uniquely positioned to learn from the dataset of queries aggregated from the Summon service generated by millions of users at hundreds of libraries around the world.

In this session, we will describe our Relevance Metrics Framework and provide examples of insights gained during its development and implementation. We will also cover recent product changes inspired by these insights. Chandra and Ted, from the Summon dev team, will share insights and outcomes from this ongoing process and highlight how analysis of large-scale query logs helps improve the academic research experience.

== Supporting Gaming in the College Classroom ==

*Megan O'Neill, Albion College, moneill AT albion DOT edu

Faculty are increasingly interested both in teaching with games and with gamifying their courses. Introducing digital games and game support for faculty through the library makes a lot of sense, but it comes with a thorny set of issues. This talk will discuss our library's initial steps toward creating a digital gamerspace and game support infrastructure in the library, including:
1) The scope and acquisitions decisions that make the most sense for us, and 2) Some difficulties we've discovered in trying to get our collection, physical- , digital- and head-space, and infrastructure up and going.
There will also be an extremely brief overview of WHY we decided to teach with games and to support gamification, what (if anything) to do about mobile gaming, and where games in education might be going.

== Codecraft ==

* Devon Smith, OCLC Research, smithde@oclc.org

We can think of and talk about software development as science, engineering, and craft. In this presentation, I'll talk about the craft aspect of software. From Wikipedia[1]: "In English, to describe something as a craft is to describe it as lying somewhere between an art (which relies on talent and technique) and a science (which relies on knowledge). In this sense, the English word craft is roughly equivalent to the ancient Greek term techne." Of the questions who, what, where, why, when, and how, I will focus on why and how, with a minor in where.

'''N.B.''': This will be a NON-TECHNICAL talk.

[1] https://en.wikipedia.org/wiki/Craft#Classification

== KnowBot: A Tool to Manage Reference and Beyond ==

* Sarah Park, Northwest Missouri State University
* Hong Gyu Han, Northwest Missouri State University
* Lori Mardis, Northwest Missouri State University

Northwest Missouri State University has developed and used RefPole for collecting and analyzing reference statistics since 2005. RefPole was a tool to answer librarians’ needs to manage reference statistics and knowledge among librarians. It was an analysis tool for the library leaders to make decisions on library operations. RefPole was adequate for the internal use; however, it was developed for local access which keeps the collective reference knowledge from being shared beyond the desktop and from being accessed by students and faculty.

In 2011, responding to growing internal and external need, the library has developed a web based knowledge base management system, KnowBot, in Ruby on Rail. KnowBot offers public searching, rating, cloud tagging, librarian, and reporting interfaces. With the additional public interfaces, it also extended reference services 24/7. Librarians can record responses to questions with graphics and multimedia. The reporting interface features not only the simple transactional data, but it also exhibits multi-dimensional analytic tool in real time.

The presenters will demonstrate KnowBot; share the source code; and discuss the use of the knowledge base to answer the organizational and public need.

== Creating a (mostly) integrated Patron Account with SirsiDynix Symphony and ILLiad ==

* Emily Lynema, North Carolina State University Libraries, ejlynema AT ncsu DOT edu
* Jason Raitz, North Carolina State University Libraries, jcraitz AT ncsu DOT edu

IIn 2012, the NCSU Libraries at long last replaced a vendor “my account” tool that had been running unsupported for years. With the opportunity to create something new, one of the initial goals was a user experience that more seamlessly combined ILS data from SirsiDynix Symphony with ILL data from ILLiad. As a Kuali OLE beta partner, the NCSU Libraries is looking at an ILS migration within the next few years, so another goal was to build the interface on top of a standard so it would not have to be re-written as part of the migration. And the icing on the cake was a transition from a local Perl-based authentication system to the newer campus-wide Shibboleth authentication.

This presentation will start with our design goals for a new user interface, include a demonstration, and describe the simple techniques used to provide a more integrated view of Symphony and ILLiad patron data. The backbone of the actual application is built using Zend’s PHP Framework and integrates eXtensible Catalog’s NCIP Toolkit to reach out to Symphony for patron data. In addition, we can talk about our successes (and difficulties) using jQuery Mobile to create a mobile view using the same underlying code as the web version. As one of our first Shibboleth applications here in the Libraries, this experience also taught us first-hand about some of the challenges of this type of single sign-on.

== SKOS Name Authority in a DSpace Institutional Repository ==

* Tom Johnson, Oregon State University, thomas.johnson@oregonstate.edu

Name ambiguity is widespread in institutional repositories. Searching by author, users are typically greeted by a variety of misspellings and permutations of initials, collision between contributors with similar names, and other problems inherent in uncontrolled (often user-submitted) data. While DSpace has the technical capacity to use controlled names, it relies on outside authority files (from LoC, for example) to do the heavy lifting. For institutional authors, this leaves a major coverage gap and creates namespace pollution on a vast scale (try searching [http://authorities.loc.gov authorities.loc.gov] for "Johnson, John", sometime).

OSU is solving this problem with an institutionally scoped, low maintenance SKOS/FOAF "name authority file". People in the IR are assigned URIs, names are maintained as skos:prefLabel, altLabel, or hiddenLabel. We've developed a simple Python application allowing staff to update individual "records", and code on the DSpace side to access the dataset over SPARQL. This presentation will walk you through where we are now, limitations we've run into, and possibilities for the future.

== Meta-Harvesting: Harvesting the Harvesters ==

* Steven Anderson, Boston Public Library, sanderson AT bpl DOT org
* Eben English, Boston Public Library, eenglish AT bpl DOT org

The emerging Digital Public Library of America (http://dp.la/) has proposed to aggregate digital content for search and discovery from several regional "service hubs" that will provide metadata via an as-yet-unspecified harvest process. As these service hubs are already harvesters of digital content from myriad sources themselves, the potential for "telephone game"-esque data loss and/or transmutation is a significant danger.

This talk will discuss the experience of Digital Commonwealth (http://www.digitalcommonwealth.org/), a statewide digital repository currently in the process of being revamped, refactored, and redesigned by the Boston Public Library using the Hydra Framework. The repository, which aggregates data from over 20 institutions (some of which are themselves aggregators), is also undergoing a massive metadata cleanup effort as records are prepared to be ingested into the DPLA as one of the regional service hubs. Topics will include automated and manual processes for data crosswalking and cleanup, advanced OAI-PMH chops, and the implications of the (at this time still-emerging) metadata standards and APIs being created by the DPLA.

Every crosswalk, transformation, migration, harvest, or export/ingest of metadata requires informed decision making and precise attention to detail. This talk will provide insight into key decision points and potential quagmires, as well as a discussion of the challenges of dealing with heterogeneous data from a wide variety of institutions.

== Pay No More Than £3 // DIY Digital Curation ==

* Chris Fitzpatrick, World Maritime University, cf AT wmu DOT se

Are you a small library or archive? <br>
Do you feel you are being held back by limited technical resources?<br>
Tired of waiting around for the Google Books Library people to reply to your emails? <br>

Join the club. Open-source software, hackerspaces, dirt cheap storage, cloud computing, and social media make it possible for any institution to start curating digitally. Today.
This talk will cover some of the guerrilla tactics being employed to drag a small university's large collection into the internet age.

Topics will include:
*Cheap and effective document scanning methods.
*Valuable resources found at your local hackerspace / makerspace / fablab.
*Metadata enrichment for the not-so-rich and NLP for the people.
*Utilizing social media to crowdsource your collection building.
*How to post-process, OCR, PDF, and ePub your documents using Free software.
*Ways to build out a digital repository with no servers, code, or large 2-year grants required. (ok, maybe some code).

== IIIF: One Image Delivery API to Rule Them All ==

* Willy Mene, Stanford University Libraries, wmene AT stanford DOT edu
* Stuart Snydman, Stanford University Libraries, snydman AT stanford DOT edu

The International Image Interoperability Framework was conceived of by a group of research and national libraries determined to achieve the holy grail of seamless sharing and reuse of images in digital image repositories and applications. By converging on common API’s for image delivery, metadata transmission and search, it is catalyzing the development of a new wave of interoperable image delivery software that will surpass the current crop of image viewers, page turners, and navigation systems, and in so doing give scholars an unprecedented level of consistent and rich access to image-based resources across participating repositories.

The IIIF Image API (http://library.stanford.edu/iiif/image-api) specifies a web service that returns an image in response to a standard http or https request. The URL can specify the region, size, rotation, quality characteristics and format of the requested image. A URL can also be constructed to request basic technical information about the image to support client applications. The API could be adopted by any image repository or service, and can be used to retrieve static images in response to a properly constructed URL.

In this presentation we will review version 1 of the IIIF image api and validator, demonstrate applications by daring early adopters, and encourage widespread adoption.

== Data-Driven Documents: Visualizing library data with D3.js ==

* Bret Davidson, North Carolina State University Libraries, bret_davidson@ncsu.edu

Several JavaScript libraries have emerged over the past few years for creating rich, interactive visualizations using web standards. Few are as powerful and flexible as D3.js[1]. D3 stands apart by merging web standards with a rich API and a unique approach to binding data to DOM elements, allowing you to apply data-driven transformations to a document. This emphasis on data over presentation has made D3 very popular; D3 is used by several prominent organizations including the New York Times[2], GOV.UK[3], and Trulia[4].

Power usually comes at a cost, and D3 makes you pay with a steeper learning curve than many alternatives. In this talk, I will get you over the hump by introducing the core construct of D3, the Data-Join. I will also discuss when you might want to use D3.js, share some examples, and explore some advanced utilities like scales and shapes. I will close with a brief overview of how we are successfully using D3 at NCSU[5] and why investing time in learning D3 might make sense for your library.

*[1]http://d3js.org/
*[2]http://www.nytimes.com/interactive/2012/08/24/us/drought-crops.html
*[3]https://www.gov.uk/performance/dashboard
*[4]http://trends.truliablog.com/vis/pricerange-boston/
*[5]http://www.lib.ncsu.edu/dli/projects/spaceassesstool

== ''n'' Characters in Search of an Author ==

* Jay Luker, IT Specialist, Smithsonian Astrophysics Data System, jluker@cfa.harvard.edu

When it comes to author names the disconnect between our metadata and what a user might enter into a search box presents challenges when trying to maximize both precision and recall [0]. When indexing a paper written by "Wäterwheels, A" a goal should be to preserve as much as possible the original information. However, users searching by author name may frequently omit the diaeresis and search for simply, "Waterwheels". The reverse of this scenario is also possible, i.e., your decrepit metadata contains only the ASCII, "Supybot, Zoia", whereas the user enters, "Supybot, Zóia". If recall is your highest priority the simple solution is to always downgrade to ASCII when indexing and querying. However this strategy sacrifices precision, as you will be unable to provide an "exact" search, necessary in cases where "Hacker, J" and "Häcker, J" really are two distinct authors.

This talk will describe the strategy ADS[1] has devised for addressing common and edge-case problems faced when dealing with author name indexing and searching. I will cover the approach we devised to not only the transliteration issue described above, but also how we deal with author initials vs. full first and/or middle names, authors who have published under different forms of their name, authors who change their names (wha? people get married?!). Our implementation relies on Solr/Lucene[2], but my goal is an 80/20 mix of high- vs. low-level details to keep things both useful and stackgnostic [3].

*[0] http://en.wikipedia.org/wiki/Precision_and_recall
*[1] http://www.adsabs.harvard.edu/
*[2] http://lucene.apache.org/solr/
*[3] http://en.wikipedia.org/wiki/Portmanteau

== But, does it all still work : Testing Drupal with simpletest and casperjs ==

* David Kinzer - Lead Developer, Jenkins Law Library, dkinzer@jenkinslaw.org
* Chad Nelson - Developer, Jenkins Law Library, cnelson@jenkinslaw.org

Most developers know that they should be writing tests along with their code, but not every developer knows how or where to get started. This talk will walk through the nuts and bolts of the testing a medium-sized Drupal site with many integrated moving parts. We’ll talk about unit testing of individual functions with [http://www.simpletest.org/en/overview.html SimpleTest] (and how that has changed how we write functions), functional testing of the user interface with [http://casperjs.org/ casperjs]. We will discuss automating deployment with [http://www.phing.info/ phing], [http://drupal.org/project/drush drush], [http://jenkins-ci.org/ jenkins-ci] & github, which, combined with our tests, removes the “hold-your-breath” feeling before updating our live site.

[[Category:Code4Lib2013]]

== Relations, Recommendations and PostgreSQL ==

* William Denton, Web Librarian, York University, wdenton@yorku.ca
* Dan Scott, Systems Librarian, Laurentian University, dscott@laurentian.ca

In 2012, a ragtag group of library hackers from various Ontario
universities, funded with only train tickets and fueled with Tim Hortons
coffee, assembled under the Scholars Portal banner to build a common
circulation data repository and recommendation engine: the Scholars
Portal Library Usage-based Recommendation Engine (SPLURGE). PostgreSQL,
the emerging darling of the old-school relational database world, is the
heart of SPLURGE, and the circulation data for Ontario's 400,000
university students is its blood. Two of the contributors to this effort explore the PostgreSQL features
that SPLURGE uses to ease administration efforts, simplify application
development, and deliver high performance results. If you don't use
PostgreSQL for your data, you might want to try it after this
presentation; if you already do, you'll pick up some new tips and tricks.

[[Category:Code4Lib2013]]