You are here

Feed aggregator

collidoscope: W3IDs for ISIL

planet code4lib - Tue, 2015-07-07 00:00
W3IDs for ISIL

The International Standard Identifier for Libraries and Related Organisations (ISIL / ISO 15511) identifies an organization, i.e. a library, an archive, a museum or a related organization, or one of its subordinate units. The registration of ISILs takes place at the National ISIL Allocation Agencies (see list).

Todays identification is best expressed through HTTP URIs because of their uniqueness. Unfortunately the distributed maintenance of ISILs in the different national agencies makes it yery hard or impossible to reference cultural heritage organizations by ISIL through URIs.

However some agencies provide ISIL-URIs or even linked data services (see Code List for Cultural Heritage Organizations or Linked Data Service Adressdaten). But wouldn’t it be nice to access cultural heritage organizations within a single domain?

Permanent Identifiers for the Web (w3id.org) provides a secure, permanent URL re-direction service for Web applications. And this gives us the opportunity to provide a single access point to organization information identified by ISIL.

One can now reference an organization identified by an ISIL through

https://w3id.org/isil/<ISIL>

Such an URI may be not dereferenceable (no data for lookup). E.g. https://w3id.org/isil/CH-000015-0 will not return any organization data but may be used as an identifier for the “Schweizerisches Literaturarchiv, Bern”.

Current ISILs that are supported for dereferencing are:

District Dispatch: So, what does a Google Policy Fellow actually… do?

planet code4lib - Mon, 2015-07-06 21:00

Guest post by Johnna Percell, 2015 Google Policy Fellow

I have spent much of my time over the past few weeks answering that question. From well-meaning family members curious about my unfamiliar career trajectory to strangers caught off guard by my answer to the classic DC introductory question – “And what do you do?” Typically telling them that I’m working at the American Library Association’s Office for Information Technology Policy (OITP) not only adds to their confusion but also provides an excellent opportunity to talk about the important work of libraries.

Albert Einstein Memorial at the National Academies.

What has been most surprising to me is how often my conversations with librarians tend to mirror the confusion of those unfamiliar with the field. My fellow librarians are already aware of the integral role libraries play in supporting the community, defending equal access to information, and bridging the digital divide. However, a surprising number of them don’t seem aware of the important policy work OITP does to ensure that libraries can best fulfill this obligation to the public.

As I wrap up my first month here at the Washington Office I thought I’d take some time to introduce myself, let you know what I’ve been doing with my time, and give you a little glimpse into the vital role policy plays in libraryland.

A little about me – I am a recent graduate of the University of Maryland’s College of Information Studies where I received my MLS with a specialization in Information and Diverse Populations. During my time at Maryland I had the pleasure of serving as president of iDiversity, the first LIS student group that promotes awareness of diversity, inclusivity, and accessibility within the information professions. Prior to beginning my Master of Library Science, I worked as an Education Coordinator for the Community Corrections Improvement Association (CCIA) in Iowa, a nonprofit organization serving the education and housing needs of individuals with community corrections involvement. My work with CCIA confirmed my interest in working to empower underserved populations and introduced me to the role libraries play as a tool to facilitate greater equality in our society.

Here at OITP this summer, I hit the ground running my first day in the office with a visit to the Federal Communications Commission (FCC) to discuss the upcoming Lifeline Modernization proceeding with Commissioner Rosenworcel and Commissioner Clyburn’s staff. The following week I tagged along to the FCC Open Commission Meeting to hear the commissioners’ plans to reform and modernize Lifeline. Now that we have our hands on the Notice of Proposed Rulemaking, I’m working my way through the proposals to see where ALA should weigh in and what role libraries can play in supporting this potentially important step toward closing the digital divide.

In addition to getting a crash-course in FCC proceedings, I’ve been able to attend a number of panel discussions and presentations to increase my understanding of the policies we’re dealing with as well as getting a glimpse into how other organizations are working on these issues. A few highlights include:

  • Kids, Learning, and Technology: Libraries as 21st Century Creative Spaces: One of the first

    A capitol chair at the congressional briefing.

    events I attended was a congressional briefing co-hosted by ALA and U.S. Representative Marcia Fudge (D-OH). It was great to see so many people (including some familiar faces from UMD!) show up to discuss the important role of libraries in advancing digital literacy in teens and exciting for me to attend my first congressional briefing. Check out Charlie Wapner’s write-up of the event on the District Dispatch last month.

  • The Future of Wifi: Public or Private?: This panel was co-hosted by the Microsoft Innovation & Policy Center and New America’s Open Technology Institute (OTI). Panelists discussed the upcoming FCC sale of spectrum bandwidth which could impact the quality of current wifi service. If you’ve ever wondered how wifi works or who owns the spectrum bands, I recommend delving into the riveting world of spectrum sales and the 2.4 GHz band. This was all new territory for me, and quite a bit more technical than I’m used to, but the implications for a large organization providing public wifi could be significant.
  • Making Mobile Broadband Affordable: Another discussion hosted by New America’s OTI. This one covered a broader view of the two major FCC initiatives that hold the potential to increase the affordability of mobile broadband. In addition to the upcoming spectrum sale, panelists discussed the Lifeline modernization proceedings. FCC Commissioner Clyburn was on hand to give the opening remarks and champion the program she has worked hard to make more effective.
  • Symposium on the Supply Chain for Middle Skill Jobs: The National Academy of Sciences hosted this two-day gathering to discuss a variety of innovative pathways to increase employment and income stability of middle skill employees. A video recording will be available in a few weeks on their site. If you want to get inspired about the important things happening to improve this portion of the job sector, I recommend streaming a few of these conversations.

The rest of my time has been spent researching the important role rural libraries play in their communities to support the Policy Revolution! initiative. I am reading up on the relevant research and reaching out to some rural librarians to get their insight into the needs and opportunities facing the communities they serve. If you’re a rural librarian you may be hearing from me soon!

As you can see, OITP’s work reaches into many corners of librarianship – and I’m just barely scratching the surface in my time here. There is so much more going on in the office and all of this work has direct implications for the work of librarians everywhere. Though it is easy to overlook while serving the complicated and urgent information needs of the patron right in front of you, policy decisions in Washington can seriously facilitate – or hinder – the work you do everyday. Having a group of dedicated information professionals advocating for libraries and library patrons here at the nexus of policy-making is indispensable to information professionals everywhere.

So what does a Google Policy Fellow do? Her very best to help advance our field.

The post So, what does a Google Policy Fellow actually… do? appeared first on District Dispatch.

LITA: LITA at ALA Annual, give us your opinions

planet code4lib - Mon, 2015-07-06 19:56

Did you attend the 2015 ALA Annual conference in San Francisco?

Thank you! There were loads of dynamic, useful and fun LITA programming at the conference. Now we want your opinions. Please complete our

LITA at ALA Annual conference survey!

LITA programs included:

  • 3 preconferences
  • Sunday afternoon with LITA inlcuding the Top Technology Trends panel
  • Rachel Vacek’s presidents program with Lou Rosenfeld
  • A total of 20 programs
  • LITA Interest Groups discussions and meetings

You can review the LITA Highlights page for information on LITA programs and activities at Annual Conference, with the link to the full conference scheduler, and check out the LITA Interest Groups special managed discussions list too.

We’re trying very hard to make sure LITA programming meets your needs. To help us we have an

Evaluation Survey for all LITA Programs at 2015 ALA Annual conference.

Now that you attended Annual we hope you’ll take the few minutes to complete the survey. The results can have a direct effect on future programming from LITA.

Question or Comments?

For questions or comments contact Mark Beatty, LITA Programs and Marketing Specialist at mbeatty@ala.org or (312) 280-4268.

Islandora: Islandora Conference - The Logo

planet code4lib - Mon, 2015-07-06 19:46

We have a little news for the upcoming Islandora Conference, taking place August 3rd to 7th on the campus of UPEI.

A few weeks ago, we got word of an amazing quote from a colleague at York University, who said, "When you fail to mention the #Islandora conference to a potential attendee, a lobster dies of sadness."

There was no way to respond except with Crayola markers and soulful lobster eyes:

Last week our conference team got together to discuss what should go on the t-shirt, and that poor sad lobster just would not go away. He did, however, change his mood to suit t-shirts that will be worn by folks who are going to the conference. We proudly present the logo for the First Annual Islandora Conference:

We hope you'll join us in Charlottetown next month and wear him proudly. Registration is still open!

HangingTogether: University reputation and ranking — getting the researchers on board

planet code4lib - Mon, 2015-07-06 18:48

In the first of this series of blog posts about the OCLC Research Library Partnership June meeting in San Francisco, Jim compared the US to other parts of the world in terms of their engagement with research reputation and ranking.  He highlighted one of the things that was common to all of the geographic areas represented at the meeting:  the need for a balance between compliance and service goals.  The library does not want to be seen by researchers as a cop enforcing mandates and gathering assessment data, but rather as a source of support for, if not collaboration in, their research.  As Google Scholar’s Anurag Acharya put it, “Conflicting imperatives abound.”

To ensure that researchers are motivated to participate in activities that contribute to university reputation and ranking, the services we design to meet reputation and ranking goals need to deliver benefits to researchers.  Some of the ways libraries can offer benefits that resonate with researchers are:

  • Reduce the number of times they have to input data.  Register them with ORCID and ISNI.  Assign DOIs for their outputs.  And libraries should speak with a unified voice in attempting to get key research workflow tools to output information as input to other systems.
  • Leverage the library’s mastery of data by populating the profile system, creating personal bibliographies, helping them to find collaborators.  Make sure to accommodate multiple contributors and their roles.  Automate processing, but allow researcher to edit.  Look at how popular Google Scholar is and emulate some of its features locally.
  • Offer guidance on increasing the impact of their work and deploying their outputs where they will receive better exposure.

Measurement of impact favors the sciences by focusing on citation in high-impact STEM journals.  The library can be an ally in providing a more complete record of scholarship by:

  • Including monographs, performances, and other forms of output for arts and humanities disciplines.
  • Considering how awards, tech transfer, and altmetrics fit into the picture.
  • Finding ways to highlight interdisciplinary and global studies.
  • Considering including staff and student research.
  • Working with other libraries to get vendors to incorporate other sources (humanities and social science indexes, WorldCat, etc.) into their systems.

The Library is often seen as a neutral party and therefore could be instrumental in promoting reputation, ranking, and related services on campus. Here are some ways to grease the skids:

  • Take advantage of the library’s space and the library’s power to convene
  • Talk about what you can do, not how you can do it (i.e., don’t use words like: hydra/fedora, infrastructure, IR)
  • By streamlining processes, turn the IR into an institutional bibliography into which/from which all data about research outputs flows: consolidate infrastructure, eliminate redundant work, embed the OA Policy / data management requirements within known processes, include restricted content, promote good metadata practices (full names, contributor roles, etc.), integrate data-tracking activities…
  • Be sensitive about faculty perceptions about assessment.  You may need to overcome researcher distrust of productivity measures and their anxiety about how the data will be combined and used – and who will have access to it.
  • Make your goal to tell the story of your university’s contributions to society.  Connect researchers to that story and to university ranking, both of which are based on researcher reputation.

By doing these things the library will be seen less as an “instrument of compliance” and more as a Partner in achieving the institution’s research goals.

See the presentations by Peter Schiffer, Ginny Steel, David Seaman, Catherine Mitchell, and Amy Brand from whence all these good ideas and more.  And stay tuned for our next installment of outcomes from the meeting.

 

 

About Ricky Erway

Ricky Erway, Senior Program Officer at OCLC Research, works with staff from the OCLC Research Library Partnership on projects ranging from managing born digital archives to research data curation.

Mail | Web | Twitter | LinkedIn | More Posts (39)

Hydra Project: Sufia 6.1 released

planet code4lib - Mon, 2015-07-06 14:22

We are pleased to announce that Sufia 6.1 has been released released.  A set of release notes can be found here (https://github.com/projecthydra/sufia/releases)

If you are currently using Sufia 6.0 we would recommend upgrading to Sufia 6.1 as soon as possible.  Beyond the additional features in the release a number of bugs were fixed.

Thanks to the 16 contributors for this release, which comprised 139 commits touching 187 files: Adam Wead, Michael Tribone, Gregorio Luis Ramirez, Justin Coyne, Nathan Rogers, Michael J. Giarlo, Carolyn Cole, Trey Terrell, Colin Brittle, Anna Headley, Hector Correa, E. Lynette Rayle, Chris Beer, Jeremy Friesen, Colin Gross, and Tricia Jenkins.

Hydra Project: Open Repositories 2017

planet code4lib - Mon, 2015-07-06 14:21

Of potential interest to Hydranauts

Call for Expressions of Interest in hosting the annual Open Repositories Conference, 2017

The Open Repositories Steering Committee seeks Expressions of Interest from candidate host organizations for the 2017 Open Repositories Annual Conference. Proposals from all geographic areas will be given consideration.

Important dates

The Open Repositories Steering Committee is accepting Expressions of Interest (EoI) to host the OR2017 conference until August 31st, 2015.  Shortlisted sites will be notified by the end of September 2015.

Background

Candidate institutions must have the ability to host at least a four-day conference of approximately 300-500 attendees (OR2015 held in Indianapolis, USA drew more than 400 people). This includes appropriate access to conference facilities, lodging, and transportation, as well as the ability to manage a range of supporting services (food services, internet services, and conference social events; conference web site; management of registration and online payments; etc.). The candidate institutions and their local arrangements committee must have the means to support the costs of producing the conference through attendee registration and independent fundraising. Fuller guidance is provided in the Open Repositories Conference Handbook on the Open Repositories wiki.

Expressions of Interest Guidelines

Organisations interested in proposing to host the OR2017 conference should follow the steps listed below:

  1. Expressions of Interest (EoIs) must be received by August 31st, 2015. Please direct these EoIs and any enquiries to OR Steering Committee Chair William Nixon <william.nixon@glasgow.ac.uk>.
  1. As noted above, the Open Repositories wiki has a set of pages at Open Repositories Conference Handbook (https://wiki.duraspace.org/display/or11/Open+Repositories+Conference+Handbook) which offer guidelines for organising an Open Repositories conference. Candidate institutions should pay particular attention to the pages listed at “Preparing a bid” before submitting an EoI.
  1. The EoI must include:

* the name of the institution (or institutions in the case of a joint bid)

* an email address as a first point of contact

* the proposed location for the conference venue with a brief paragraph describing the local amenities that would be available to delegates, including its proximity to a reasonably well-served airport

  1. The OR Steering Committee will review proposals and may seek advice from additional reviewers. Following the review, one or more institutions will be invited to submit a detailed proposal.
  1. Invitations to submit a detailed proposal will be issued by the end of September 2015; institutions whose interest will not be taken up will also be notified at that time. The invitations sent out will provide a timeline for submitting a formal proposal and details of additional information available to the shortlisted sites for help in the preparation of their bid.  The OR Steering Committee will be happy to answer specific queries whilst proposals are being prepared.

About Open Repositories

Since 2006 Open Repositories has hosted an annual conference that brings together users and developers of open digital repository platforms. For further information about Open Repositories and links to past conference sites, please visit the OR home page: http://sites.tdl.org/openrepositories/.

Subscribe to announcements about Open Repositories conferences by joining the OR Google Group http://groups.google.com/group/open-repositories.

Mark E. Phillips: Punctuation in DPLA subject strings

planet code4lib - Mon, 2015-07-06 14:00

For the past few weeks I’ve been curious about the punctuation characters that are being used in the subject strings in the DPLA dataset I’ve been using for some blog posts over the past few months.

This post is an attempt to find out the range of punctuation characters used in these subject strings and is carried over from last week’s post related to subject string metrics.

What got me started was that in the analysis used for last week’s post,  I noticed that there were a number of instances of em dashes “—” (528 instances) and en dashes “–” (822 instances) being used in place of double hyphens “–” in subject strings from The Portal to Texas History. No doubt these were most likely copied from some other source.  Here is a great subject string that contains all three characters listed above.

Real Property — Texas –- Zavala County — Maps

Turns out this isn’t just something that happened in the Portal data,  here is an example from the Mountain West Digital Library.

Highway planning--Environmental aspects–Arizona—Periodicals

To get the analysis started the first thing that I need to do is establish what I’m considering punctuation characters because that definition can change depending on who you are talking to and what language you are using.  For this analysis I’m using the punctuation listed in the python string module.

>>> import string >>> print string.punctuation !"#$%&'()*+,-./:;<=>?@[\]^_`{|}~

So this gives us 32 characters that I’m considering to be punctuation characters for the analysis in this post.

The first thing I wanted to do was to get an idea of which of the 32 characters were present in the subject strings, and how many instances there were.  In the dataset I’m using there are 1,871,877 unique subject strings.  Of those subject strings 1,496,769 or 80% have one or more punctuation characters present.  

Here is the breakdown of the number of subjects that have a specific character present.  One thing to note is that when processing if there were repeated instance of a character, they were reduced to a single instance, it doesn’t affect the analysis just something to note.

Character Subjects with Character ! 72 “ 1,066 # 432 $ 57 % 16 & 33,825 ‘ 22,671 ( 238,252 ) 238,068 * 451 + 81 , 607,849 – 954,992 . 327,404 / 3,217 : 10,774 ; 5,166 < 1,028 = 1,027 > 1,027 ? 7,005 @ 53 [ 9,872 ] 9,893 \ 32 ^ 1 _ 80 ` 99 { 9 | 72 } 9 ~ 4

One thing that I found interesting is that characters () and [] have different numbers of instances suggesting there are unbalanced brackets and parenthesis in subjects somewhere.

Another interesting note is that there are 72 instances of subjects that use the pipe character “|”.  The pipe is often used by programmers and developers as a delimiter because it “is rarely used in the data values”  this analysis says that while true it is rarely used,  it should be kept in mind that it is sometimes used.

Next up was to look at how punctuation was distributed across the various Hubs.

In the table below I’ve pulled out the total number of unique subjects per Hub in the DPLA dataset.  I show the number of subjects without punctuation and the number of subjects with some sort of punctuation and finally display the percentage of subjects with punctuation.

Hub Name Unique Subjects Subjects without Punctuation Subjects with Punctuation Percent with Punctuation ARTstor 9,560 6,093 3,467 36.3% Biodiversity_Heritage_Library 22,004 14,936 7,068 32.1% David_Rumsey 123 106 17 13.8% Harvard_Library 9,257 553 8,704 94.0% HathiTrust 685,733 56,950 628,783 91.7% Internet_Archive 56,910 17,909 39,001 68.5% J._Paul_Getty_Trust 2,777 375 2,402 86.5% National_Archives_and_Records_Administration 7,086 2,150 4,936 69.7% Smithsonian_Institution 348,302 152,850 195,452 56.1% The_New_York_Public_Library 69,210 9,202 60,008 86.7% United_States_Government_Printing_Office_(GPO) 174,067 14,525 159,542 91.7% University_of_Illinois_at_Urbana-Champaign 6,183 2,132 4,051 65.5% University_of_Southern_California._Libraries 65,958 37,237 28,721 43.5% University_of_Virginia_Library 3,736 1,099 2,637 70.6% Digital_Commonwealth 41,704 8,381 33,323 79.9% Digital_Library_of_Georgia 132,160 9,876 122,284 92.5% Kentucky_Digital_Library 1,972 579 1,393 70.6% Minnesota_Digital_Library 24,472 16,555 7,917 32.4% Missouri_Hub 6,893 2,410 4,483 65.0% Mountain_West_Digital_Library 227,755 84,452 143,303 62.9% North_Carolina_Digital_Heritage_Center 99,258 9,253 90,005 90.7% South_Carolina_Digital_Library 23,842 4,002 19,840 83.2% The_Portal_to_Texas_History 104,566 40,310 64,256 61.5%

To make it a little easier to see I make a graph of this same data and divided the graph into two groups,  on the left are the Content-Hubs and the right are the Service-Hubs.

Percent of Subjects with Punctuation

I don’t see a huge difference between the two groups and the percentage of punctuation in subjects, at least by just looking at things.

Next I wanted to see out of the 32 characters that I’m considering in this post,  how many of those characters are present in a given hubs subjects.  That data is in the table and graph below.

Hub Name Characters Present ARTstor 19 Biodiversity_Heritage_Library 20 David_Rumsey 7 Digital_Commonwealth 21 Digital_Library_of_Georgia 22 Harvard_Library 12 HathiTrust 28 Internet_Archive 26 J._Paul_Getty_Trust 11 Kentucky_Digital_Library 11 Minnesota_Digital_Library 16 Missouri_Hub 14 Mountain_West_Digital_Library 30 National_Archives_and_Records_Administration 10 North_Carolina_Digital_Heritage_Center 23 Smithsonian_Institution 26 South_Carolina_Digital_Library 16 The_New_York_Public_Library 18 The_Portal_to_Texas_History 22 United_States_Government_Printing_Office_(GPO) 17 University_of_Illinois_at_Urbana-Champaign 12 University_of_Southern_California._Libraries 25 University_of_Virginia_Library 13

Here is this data in a graph grouped in Content and Service Hubs.

Unique Punctuation Characters Present

Mountain West Digital Library had the most characters covered with 30 of the 32 possible punctuation characters. One the low end was the David Rumsey collection with only 7 characters represented in the subject data.

The final thing is to see the character usage for all characters divided by hub so the following graphic presents that data.  I tried to do a little coloring of the table to make it a bit easier to read, don’t know how well I accomplished that.

Punctuation Character Usage (click to view larger image)

So it looks like the following characters ‘(),-. are present in all of the hubs.  The characters %/?: are present in almost all of the hubs (missing one hub each).

The least used character is the ^ which is only in use by one hub in one record.  The characters ~ and @ are only used in two hubs each.

I’ve found this quick look at the punctuation usage in subjects pretty interesting so far,  I know that there were some anomalies that I unearthed for the Portal dataset with this work that we now have on the board to fix,  they aren’t huge issues but things that probably would stick around for quite some time in a set of records without specific identification.

For me the next step is to see if there is a way to identify punctuation characters that are used incorrectly and be able to flag those fields and records in some way to report back to metadata creators.

Let me know what you think via Twitter if you have questions or comments.

 

Terry Reese: MarcEdit OSX Public Preview 1

planet code4lib - Mon, 2015-07-06 03:40

It’s with a little trepidation that I’m formally making the first Public Preview of the MarcEdit OSX version available for download and use.  In fact, as of today, this version is now *the* OSX download available on the downloads page.  I will no longer be building the old code-base for use on OSX.

When I first started this project around Mid-April, I began knowing that this process would take some time.  I’ve been working on MarcEdit continuously for a little over 16 years.  It’s gone through one significant rewrite (when the program moved from Assembly to C#) and has had way too many revisions to count.  In agreeing to take on the porting work — I’d hoped that I could port a significant portion of the program over the course of about 8 months and that by the end of August, I could produce a version of MarcEdit that would cover the 80% or so of the commonly used application toolset.  To do this, it meant porting the MARC Tools portion of the application and the MarcEditor.

Well, I’m ahead of schedule.  Since about 2014, I’ve been reworking a good deal of the application to support a smoother porting process sometime in the future — though, honestly, I wasn’t sure that I’d ever actual do the porting work.  Pleasantly, this early work has made a good deal of the porting work easier allowing me to move faster than I’d anticipated.  As of this posting, a significant portion of that 80% has been converted, and I think that for many people — most of what they probably use daily — has been implemented.  And while I’m ahead of schedule and have been happy with how the porting process has gone, make no mistake — it’s been a lot of work, and a lot of code.  Even though this work has primarily been centered around rewriting just the UI portions of MarcEdit, you are still talking, as of today, close to 200,000 lines of code.  This doesn’t include the significant amount of work I’ve done around the general assemblies that have provided improvements to all MarcEdit users.  Because of that — I need to start getting feedback from users.  While the general assemblies go through an automated testing process — I haven’t, as of yet, come up with an automated testing process for the OSX build.  This means that I’m testing things manually, and simply cannot go through the same leveling of testing that I do each time I build the Windows version.  Most folks may not realize it, but it takes about a day to build the Windows version — as the program goes through various unit tests processing close to 25 million records.  I simply don’t have an equivalent of that process yet, so I’m hoping that everyone interested in this work will give it a spin, use it for real work, and let me know if/when things fall down.

In creating the Preview, I’ve tried to make the process for users as easy as possible.  Users interested in running the program simply need to be running at least OSX 10.8 and download the dmg found here: http://marcedit.reeset.net/downloads.  Once downloaded, run the dmg an a new disk will mount called MarcEdit OSX.  Run this file, and you’ll see the following installer:

MarcEdit OSX installer

Drag the MarcEdit icon into the Applications folder and the application will either install, or overwrite an existing version.  That’s it.  No other downloads are necessary.  On first run, the program will generate a marcedit folder under /users/[yourid]/marcedit.  I realize that this isn’t completely normal — but I need the data accessible outside of the normal app sandbox to easily support updates.  I’d also considered the User Documents folder, but the configuration data probably shouldn’t live there either.  So, this is where I ended up putting it.

So what’s been completed — Essentially, all the MARC Tools functions and a significant amount of the MarcEditor has been completed.  There are some conspicuous functions that are absent at this point though.  The Call Number and Fast Heading generation, the Delimited Text Translator and Exporter, the Select and Delete Selected Records, everything Z39.50 related, as well as the Linked Data tools and the Integration work with OCLC and Koha.  All these are not currently available — but will be worked on.  At this point, what users can do is start letting me know what absent components are impacting you the most, and I’ll see how they fit into the current development roadmap.

Anyway — that’s it.  I’m excited to let you all give this a try, and a little nervous as well.  This has been a significant undertaking which has definitely pushed me a bit, requiring me to learn Object-C in a short period of time, as well as quickly assimilate a significant portion of Apples SDK documents relating to UI design.  I’m sure I’ve missed things, but it’s time to let other folks start working with it.

If you have been interested in this work — download the installer, kick the tires, and give feedback.  Just remember to be gentle.  

–TR

Download URL: http://marcedit.reeset.net/downloads

 

Terry Reese: MarcEdit 6.1 Update

planet code4lib - Mon, 2015-07-06 03:33

This was something I’d hoped to get into the last update, but didn’t get the time to test it; so I got it done now.  While at the first MarcEdit User Group meeting at ALA, there was a question about supporting 880 fields when exporting data via tab delimited format.  When you use the tool right now, the program will export all the 880 fields, not a specific 880 field.  This update changes that.  After the update, when you select the 880 field in the Export tab delimited tool, the program will ask you for the linking field.  In this case, the program will then match the 880$6[linkingfield], and pull the selected subfield.  I’m not sure how often this comes up — but it certainly made a lot of sense when the problem was described to me.

You can pick up the download at: http://marcedit.reeset.net/downloads

–tr

DuraSpace News: Quarterly Report from Fedora, January - June 2015

planet code4lib - Mon, 2015-07-06 00:00

From The Fedora Leadership Group

Fedora Development

In the past two quarters, the development team released three new versions of Fedora 4; detailed release notes are here:

Open Library Data Additions: PACER dump of cofc (Court of Federal Claims)

planet code4lib - Sun, 2015-07-05 17:56

PACER records from The U.S. Court of Federal Claims..

This item belongs to: data/ol_data.

This item has files of the following types: Data, Data, Metadata

Patrick Hochstenbach: Homework assignment #7 Sketchbookskool #BootKamp

planet code4lib - Sun, 2015-07-05 07:15
Filed under: Sketchbook Tagged: sketch, sketchbook, sketchbookskool, urbansketching

Jonathan Rochkind: Long-standing bug in Chrome (WebKit?) on page not being drawn, scroll:auto, retina

planet code4lib - Sat, 2015-07-04 13:57

In a project I’m recently working on, I ran into a very odd bug in Chrome (may reproduce in other WebKit browsers, not sure).

My project loads some content via AJAX into a portion of the page. In some cases, the content loaded is not properly displayed, it’s not actually painted by the browser. There is space taken up by it on the page, but it’s kind of as if it had `display:none` set, although not quite like that because sometimes _some_ of the content is displayed but not others.

Various user interactions will force the content to paint, including resizing the browser window.

Googling around, there are various people who have been talking about this bug, or possibly similar bugs, for literally years. Including here and maybe this is the same thing or related, hard to say.

think the conditions that trigger the bug in my case may include:

  • A Mac “retina” screen, the bug may not trigger on ordinary resolutions.
  • Adding/changing content via Javascript in a block on the page that has been set to `overflow: auto` (or just overflow-x or overflow-y auto).

I think both of these things are it, and it’s got something to do with Chrome/WebKit getting confused calculating whether a scrollbar is neccesary (and whether space has to be reserved for it) on a high-resolution “retina” screen, when dynamically loading content.

It’s difficult to google around for this, because nobody seems to quite understand the bug. It’s a big dismaying though that it seems likely this bug — or at least related bugs with retina screens, scrollbar calculation, dynamic content, etc — have existed in Chrome/WebKit for possibly many years.  I am not certain if any tickets are filed in Chrome/WebKit bug tracker on this (or if anyone’s figured out exactly what causes it from Chrome’s point of view).  (this ticket is not quite the same thing, but is also about overflow calculations and retina screens, so could be caused by a common underlying bug).

There are a variety of workarounds suggested on Google, for bugs with Chrome not properly painting dynamically loaded content. Some of them didn’t seem to work for me; others cause a white flash even in browsers that wouldn’t otherwise be effected by the bug; others were inconvenient to apply in my context or required a really unpleasant `timeout` in JS code to tell chrome to do something a few dozen/hundred ms after the dynamic content was loaded. (I think Chrome/WebKit may be smart enough to ignore changes that you immediately undo in some cases, so they don’t trigger any rendering redraw; but here we want to trick Chrome into doing a rendering redraw without actually changing the layout, so, yeah).

Here’s the hacky lesser evil workaround which seems to work for me. Immediately after dynamically loading the content, do this to it’s parent div:

$("#parentDiv").css("opacity", 0.99999).css("opacity", 1.0);

It does leave a `style` element setting opacity to 1.0 sitting around on your parent container after you’re done, oh well.

I haven’t actually tried the solution suggested here, to a problem which may or may not be the same one I have — of simply adding `-webkit-transform: translate3d(0,0,0)` to relevant elements.

One of the most distressing things about this bug is if you aren’t testing on a retina screen (and why/how would you unless your workstation happens to have one), you may not ever notice or be able to reproduce the bug, but you may be ruining the interface for users on retina screens (and find their bug report completely unintelligible and unreproducible if they do report it, whether or not they mention they have a retina screen when they file it, which they probably won’t, they may not even know what this is, let alone guess it’s a pertinent detail).

Also that the solutions are so hacky that I am not confident they won’t stop working in some future version of Chrome that still exhibits the bug.

Oh well, so it goes. I really wish Chrome/WebKit would notice and fix though. Probably won’t happen until someone who works on Chrome/WebKit gets a retina screen and happens to run into the bug themselves.


Filed under: General

FOSS4Lib Recent Releases: ePADD - 1.0

planet code4lib - Fri, 2015-07-03 21:25

Last updated July 3, 2015. Created by Peter Murray on July 3, 2015.
Log in to edit this page.

Package: ePADDRelease Date: Wednesday, July 1, 2015

FOSS4Lib Updated Packages: ePADD

planet code4lib - Fri, 2015-07-03 21:22

Last updated July 3, 2015. Created by Peter Murray on July 3, 2015.
Log in to edit this page.

ePADD is a software package developed by Stanford University's Special Collections & University Archives that supports archival processes around the appraisal, ingest, processing, discovery, and delivery of email archives.

The software is comprised of four modules:

Appraisal: Allows donors, dealers, and curators to easily gather and review email archives prior to transferring those files to an archival repository.

Processing: Provides archivists with the means to arrange and describe email archives.

Discovery: Provides the tools for repositories to remotely share a redacted view of their email archives with users through a web server discovery environment. (Note that this module is downloaded separately).

Delivery: Enables archival repositories to provide moderated full-text access to unrestricted email archives within a reading room environment.

Package Type: Archival Record Manager and EditorLicense: Apache 2.0 Package Links Development Status: Production/StableOperating System: LinuxMacWindows Releases for ePADD Technologies Used: SOLRTomcatProgramming Language: JavaOpen Hub Link: https://openhub.net/p/epaddOpen Hub Stats Widget: 

FOSS4Lib Recent Releases: Sufia - 6.1.0

planet code4lib - Fri, 2015-07-03 21:15

Last updated July 3, 2015. Created by Peter Murray on July 3, 2015.
Log in to edit this page.

Package: SufiaRelease Date: Thursday, July 2, 2015

Open Library Data Additions: Amazon Crawl: part if

planet code4lib - Fri, 2015-07-03 13:58

Part if of Amazon crawl..

This item belongs to: data/ol_data.

This item has files of the following types: Data, Data, Metadata, Text

DPLA: Preserving the Star-Spangled Banner

planet code4lib - Fri, 2015-07-03 12:00

The tune of the “Star-Spangled Banner” is one that will be played at picnics, fireworks displays, and other Fourth of July celebrations across the country this weekend. But the “broad stripes and bright stars” of the original flag that flew over Fort McHenry in 1814–inspiring Francis Scott Key to pen the iconic poem–have required some refreshing over the years. While recent conservation efforts have made the flag a centerpiece of the Smithsonian’s climate-controlled Flag Hall at the National Museum of American History, that wasn’t the only big upkeep project on the flag. Here’s the story behind the 1914 conservation effort spearheaded by a talented embroidery teacher to bring new life to an American icon.

Women at work repairing the Star-Spangled Banner, 1914. Courtesy of The New York Public Library.

The Star-Spangled Banner first came to the Smithsonian in 1907 and  was formally gifted a few years later from the family of Lieutenant Colonel George Armistead. When it came to the museum, the flag itself had seen significant damage. In addition to the battle it survived at Fort McHenry, pieces of the flag had been given out as mementos by Armistead’s family to friends, war veterans, and politicians (legend has it even to Abraham Lincoln, though his rumored piece has never been found).

The original “Star-Spangled Banner.” Courtesy of The New York Public Library.

By the time the Smithsonian’s first conservation efforts began, the flag itself was 100 years old and in fragile condition. In 1914, the Smithsonian brought on embroidery teacher and professional flag restorer Amelia Fowler (who had experience fixing historic flags at the US Naval Academy) to undertake the Star-Spangled Banner project. Fowler, alongside her team of ten needlewomen, spent eight-weeks in the humid early summer restoring the flag. The team took off a canvas backing that had been attached in the 1870s, when the flag was displayed at the Boston Navy Yard. Fowler attached a new linen backing, with approximately 1,700,000 stitches, in a unique honeycomb pattern–a preservation technique Fowler herself patented. For the project, Fowler was paid $500 and her team split an additional $500. The newly-preserved flag was on display for the next fifty years.

Fowler’s flag restoration, which she said would “defy the test of time,” did last until 1999, during the “Save America’s Treasures” preservation campaign, when conservation efforts began again. The extensive work that Fowler completed to revive the Star-Spangled Banner, those millions of stitches, took conservators almost two years to remove. The iconic flag remains up for display in the Smithsonian’s National Museum of American History, inspiring new generations in “the land of the free and the home of the brave.”

Featured image, 1839 sheet-music for “The Star-Spangled Banner,” courtesy of the University of North Carolina at Chapel Hill via North Carolina Digital Heritage Center.

Pages

Subscribe to code4lib aggregator