On the Child as Memoirist

Sep. 17th, 2014 10:35 am
[syndicated profile] kirkus_kidlit_feed
We recently reviewed I Am Malala, the young-readers’ edition of education activist Malala Yousafzai’s memoir, co-written by Patricia McCormick. Our reviewer tussled with the implications of criticizing the account of a Nobel Peace Prize nominee who was shot and severely injured for speaking up for the rights of girls to go to school. Talk about Worthy and Important. The trouble was that Yousafzai is so earnest and so dedicated to her cause that at times she comes across as sounding like, well, a goody-two-shoes. How do you say that? Obviously, you don’t, but just because Yousafzai is legitimately heroic doesn’t mean that she won’t strike young American readers as preachy.
[syndicated profile] aotus_feed

Posted by David Ferriero

I am pleased to announce that the Office of Management and Budget and the National Archives released a memo yesterday afternoon to the heads of executive departments and independent agencies on managing email. Over the past few weeks, this issue has been brought into focus through testimony that I delivered to the House Committee on Oversight and Government Reform. In addition, we have received questions from agencies as they are reviewing our Capstone Bulletin to determine if this approach is feasible for them. This is also important in light of the requirement in the Managing Government Records Directive (OMB M-12-18) for all email to be managed electronically by December 31, 2016.

The memo reinforces the importance for each agency to manage their email properly and includes a new NARA Bulletin to assist agencies. NARA Bulletin 2014-06 reminds agency heads of existing NARA guidance and resources to assist in managing email.  The memo also reminds agencies of the upcoming deadline in the Directive to develop suitable training for all agency personnel.

Our Office of the Chief Records Officer is leading our efforts to work with agencies to meet all the goals in the Directive. For more information about this work, and other initiatives they are undertaking, please visit their Records Express blog.… [ Read all ]

Web Components punch list

Sep. 14th, 2014 02:27 pm
[syndicated profile] paciello_a11y_feed

Posted by Steve Faulkner

Considerations for web component and custom control design:

If your control has the stuff below covered, excellent! If not then please implement it before shouting to the world about it being the next big thing. Or at least document its deficits and provide a health warning that the control is incomplete and not fit to use in production.

design consideration description Yes/No
focusable Can you get to the control via the keyboard?
operable Can you use the control with the keyboard?
expected operation Can you use the standard keys for the control type to operate it.
clear indication of focus Can you easily see it when the control has focus?
label The control has a text label that is exposed as an accessible name in accessibility APIs
role The control has an appropriate role exposed in accessibility APIs
states and properties The control has any UI states and properties that it has exposed in accessibility APIs

Take note:

The ARIA design patterns provide a most excellent and comprehensive set of requirements, for expected keyboard interaction and what role, state and property information needs to be exposed, for a large variety of custom controls.

Accessibility APIs

If the term accessibility APIs has you scratching your head, read Why accessibility APIs matter by the one and only Marco Zehe.

The accessibility tree

Tree of accessible objects that represents the structure of the user interface (UI). Each node in the accessibility tree represents an element in the UI as exposed through the accessibility API; for example, a push button, a check box, or container.

Example baseline test using the native HTML button element

Most of the considerations listed below do not need to be checked for a native HTML button as you get them for free (thanks to the browser implementers). If you build a custom control (for example, a custom button web component) you need to add most of this stuff yourself.

design consideration description Yes/No
focusable Using a test file attempt to tab to the control. (except when it is disabled) yes
operable Using a test file attempt to make something happen (except when it is disabled) yes
expected operation Buttons have standard expected keystrokes (enter or space) that will make something happen. Using a test file ensure that controls works as expected. (except when it is disabled) yes
indication of focus Using a test file, can you see the control is focused? (except when it is disabled) yes
label Default method for providing an accessible name for button is via text content child of button element (there are others, whatever you use you you need to end up with an acc name exposed). You can check it using aViewer or other accessibility object inspection tool. yes
role Default role for <button> is already provided by browser (role:button). You can check it using aViewer or other accessibility object inspection tool yes
states and properties The control has any UI states and properties that it has exposed in accessibility APIs. Standard states and properties for <button> are already provided by browser (focusable, focused, unavailable [if disabled attribute used). You can check them using aViewer or other accessibility object inspection tool. yes

aViewer

Obect Inspection tools such as aViewer can be used to test that your custom controls are exposing the correct information via accessibility APIs.

aVIEWER UI displaying information about a button element. It shows that the button has a correct accessible name and role and state.

Some Other Object inspection tools:

A personal opinion

Further reading

 

[syndicated profile] alaskanlibrarian_feed

Posted by Daniel Cornwall

Note: You might want to check out my comment policy before proceeding as this topic has provoked a lot of emotion in the past. 


 

A major reason we (United States) invaded Iraq in 2003 was the Bush Doctrine that insisted we had to smash a future threat. Not a clear and present danger to the United States, but because of what Iraq MIGHT do to us later. We struck out of fear of the future. Because we were afraid, we kept a 100,000 troops in the country for ten years. In the process over 5,000 American soliders were killed and tens of thousands were badly injured. Estimates of Iraqi casualties vary widely, but conservatively at least 50,000 Iraqis died as a result of our invasion and occupation over and above the number who would have died if we have left well enough alone. We also spent over a trillion dollars.

Bush’s “preventive war” was a stupid, expensive and most of all, deadly idea. What did we get after a ten year occupation with 100,000 troops? A broken country that is more closely aligned with Iran than the United States.

You’d think that this deadly and experience would make us swear off “preventive war” forever. I thought so. But I was wrong. But President Obama now embraces it, in concept if not in scale. Here’s what he said in his “four point” strategy statement on 9/10/2014 (bolding mine):

So ISIL poses a threat to the people of Iraq and Syria, and the broader Middle East — including American citizens, personnel and facilities.  If left unchecked, these terrorists could pose a growing threat beyond that region, including to the United States.  While we have not yet detected specific plotting against our homeland, ISIL leaders have threatened America and our allies.  Our Intelligence Community believes that thousands of foreigners -– including Europeans and some Americans –- have joined them in Syria and Iraq.  Trained and battle-hardened, these fighters could try to return to their home countries and carry out deadly attacks.

A lot of coulds and ifs. That’s the basis that we want to carry out attacks on Syria against the wishes of that country’s admittedly unsavory government and outside of UN authorization. We violate international law and go to war on another Muslim country that is not involved in attacks on American soil because of what they MIGHT do later. That was a bad idea in 2003 and it’s a terrible idea now.

I admit that ISIL does pose a threat to the people of Iraq and Syria, but we shouldn’t be the ones carrying out military actions: There are a number of reasons why, including:

Although President Obama’s proposed war on ISIS/ISIL is much smaller than President Bush’s invasion of Iraq, it will grow in size because if we couldn’t secure peace and stability in Iraq with a ten year occupation with 100,000 troops, the President’s measures won’t work. Rather than cutting our losses, we will once again “Stay the Course” and pour more and more resources and people into the Iraqi/Syrian black hole. And for what, for what someone MIGHT do LATER? This is madness again. Congress should put the brakes on it. Only I’m afraid they want to punch the accelerator. Again.

 

 

 

 


Filed under: current events Tagged: iraq, syria, war

Facing the Music

Sep. 12th, 2014 04:19 pm
[syndicated profile] kirkus_kidlit_feed
There are, on any given day, many new picture books about children making their way, as well as picture books about music. But today I want to highlight two new ones that are about both. One is fiction—Chieri Uegaki’s Hana Hashimoto, Sixth Violin, illustrated by Qin Leng. And the other is a picture book biography, Little Melba and Her Big Trombone, written by Katheryn Russell-Brown and illustrated by Coretta Scott King/John Steptoe Award winner Frank Morrison.
[syndicated profile] paciello_a11y_feed

Posted by Steve Faulkner

The Extensible Web Summit happened in Berlin yesterday. This prompted written words from some big thinkers and doers. Jeremy Keith wrote a piece on Web Components followed up by a uncomfortably excited response from Alex Russell.

On Piffle and Tosh and feasting upon Fetid code

While I am as excited as the next nerd by the potential of web components. Their development and marketing appear to follow the same depressing pattern of ship first, oh yeah we better tack on some ARIA to cover up the cracks.

Alex stated yesterday:

Jeremy’s argument, if I can paraphrase, is that people will build Web Components and this might be bad [for accessibility].

Piffle and tosh.

I cannot but agree with Alex piffle wise. Jeremy’s argument does not go far enough.  Web components are being built in the same development culture that web stuff is usually built in, and this is bad for accessibility. This is not to say that web components are by definition bad. It is the same story for any implementation of accessibility support on the web, in browsers and in UI libraries: it usually comes after, often way after a product has been shipped and distributed to millions upon millions of people and 100s of thousands of developers have gorged on and regurgitated the code in their own projects.

Examples?

Some tweets I wrote in June (in usual diplomatic style) upon initial release of Polymer Paper web components which may well be fantastic examples of what can be achieved with this new technology, but were sadly lacking in even the most basic accessibility considerations (this situation has improved but they are still riddled with issues):

 

Alex stated yesterday:

Luckily we’ve been thinking very hard about this at Google and have invested heavily in Polymer and high-quality Material Design components that are, as I write this, undergoing review and enhancement for accessibility.

The economics of the new situation that Web Components introduce are (intentionally) tilted in a direction that provides ability for cream to rise to the top — and for the community to quickly judge if it smell off and do something about it.

As Alex stated “Google … have invested heavily in Polymer” and also invest in accessibility (see references). What I can’t comprehend is why that investment of big smarts and big bucks by Google did not include the integration of accessibility and usability into the core development cycle? Why is it considered the community’s job to polish the turds?

Further reading/watching


The Road to Recovery

Sep. 11th, 2014 06:35 pm
[syndicated profile] kirkus_ya_feed
Until recently, 15-year-old Joy had lived her entire life in a small trailer with her mother. She mostly stayed in her room to avoid unwanted attention from her mother’s friends and various live-in boyfriends—hiding didn’t always work, but it was her best option—only coming out at night or when her mother was at work in order to eat, use the bathroom, just to breathe. As her mother rarely let her outside, she’d never been to school, though the movie Matilda inspired her to enroll in her district’s homeschooling program.
[syndicated profile] library_tech_jester_feed

Posted by Peter Murray

Receive DLTJ Thursday Threads:

by E-mail

by RSS

Delivered by FeedBurner

Welcome to the latest edition of Thursday Threads. This week’s post has a continuation of the commentary about the Kuali Board’s decisions from last month. Next, news of a fundraising campaign by the Ada Initiative in support of women in technology fields. Lastly, an article that looks at the relative bulk bandwidth costs around the world.

Feel free to send this to others you think might be interested in the topics. If you find these threads interesting and useful, you might want to add the Thursday Threads RSS Feed to your feed reader or subscribe to e-mail delivery using the form to the right. If you would like a more raw and immediate version of these types of stories, watch my Pinboard bookmarks (or subscribe to its feed in your feed reader). Items posted to are also sent out as tweets; you can follow me on Twitter. Comments and tips, as always, are welcome.

Discussion about Sakai’s Shift Continues

The Kuali mission continues into its second decade. Technology is evolving to favor cloud-scale software platforms in an era of greater network bandwidth via fast Internet2 connections and shifting economics for higher education. The addition of a Professional Open Source organization that is funded with patient capital from university interests is again an innovation that blends elements to help create options for the success of colleges and universities.

Yet many of the true believers in higher education’s Open Source Community, which seeks to reduce software costs and provide better e-Learning and administrative IT applications for colleges and universities, may feel that they have little reason to celebrate the tenth anniversaries of Sakai, an Open Source Learning Management System and Kuali, a suite of mission critical, Open Source, administrative applications, both of which launched in 2004.  Indeed, for some Open Source evangelists and purists, this was probably a summer marked by major “disturbances in the force” of Open Source

- Kuali Goes For Profits by Kenneth C. Green, 9-Sep-2014, Digital Tweed blog at Inside Higher Ed

The reverberations from the decision by the Kuali Foundation Board to fork the Kuali code to a different open source license and to use Kuali capital reserves to form a for-profit corporation continue to reverberate. (This was covered in last week’s DLTJ Thursday Threads and earlier in a separate DLTJ post.) In addition to the two articles above, I would encourage readers to look at Charles Severance’s “How to Achieve Vendor Lock-in with a Legit Open Source License – Affero GPL”. Kuali is forking its code from using the Educational Community License to the Affero GPL license, which it has the right to do. It also comes with some significant changes, as Kenneth Green points out. There is still more to this story, so expect it to be covered in additional Thursday Threads posts.

Ada Initiative, Supporting Women in Open Technology and Culture, Focuses Library Attention with a Fundraising Campaign

The Ada Initiative has my back. In the past several years they have been a transformative force in the open source software community and in the lives of women I know and care about. To show our support, Andromeda Yelton, Chris Bourg, Mark Matienzo and I have pledged to match up to $5120 of donations to the Ada Initiative made through this link before Tuesday September 16. That seems like a lot of money, right? Well, here’s my story about how the Ada Initiative helped me when I needed it most.

- The Ada Initiative Has My Back, by Bess Sadler, Solvitur Ambulando blog, 9-Sep-2014

The Ada Initiative does a lot to support women in open technology and culture communities; in the library technology community alone, many women have been affected by physical and emotional violence. (See the bottom of the campaign update blog post from Ada Initiative for links to the stories.) I believe it is only decent to enable anyone to participate in our communities without fear for their physical and psychic space, and that our communities are only as strong as they can be when the barriers to participation are low. The Ada Initiative is making a difference, and I’m proud to have supported them with a financial contribution as well as being an ally and a amplifier for the voice of women in technology.

The Relative Cost of Bandwidth Around the World

The chart above shows the relative cost of bandwidth assuming a benchmark transit cost of $10/Megabits per second (Mbps) per month (which we know is higher than actual pricing, it’s just a benchmark) in North America and Europe. From CloudFlare

Over the last few months, there’s been increased attention on networks and how they interconnect. CloudFlare runs a large network that interconnects with many others around the world. From our vantage point, we have incredible visibility into global network operations. Given our unique situation, we thought it might be useful to explain how networks operate, and the relative costs of Internet connectivity in different parts of the world.

Bandwidth is cheapest in Europe and highest in Australia? Who knew? CloudFlare published this piece showing their costs on most of the world’s continents with some interesting thoughts about the role competition has on the cost of bandwidth.

When the refresh comes

Sep. 9th, 2014 01:25 pm
[syndicated profile] paciello_a11y_feed

Posted by Steve Faulkner

The Section 508 Refresh contains a provision that places responsibility on assistive technology vendors to make use of accessibility information made available via platform accessibility APIs. I suggest this is a very good thing.

Level playing field

In our shared quest to provide user interfaces that are usable by all, accessibility practitioners (such as myself) have an expectation that developers (those who build the web) and browser vendors (those that provide access to the content of the web) will build their products according to agreed standards and guidelines. If they do not then their products will be unusable by some. None of the current standards relating to accessibility appear to place any responsibility on assistive technology vendors to ensure that their products use the agreed and implemented standards, I suggest that this is a very bad thing and does not serve users well. The Section 508 refresh includes a provision to remedy this imbalance of responsibility. We cannot continue to ask much of developers and browser vendors without assistive technology vendors doing their part.

503.3 Alternative User Interfaces.

Where an application provides an alternative user interface that functions as assistive technology, the application shall use platform and other industry standard accessibility services to provide the alternate user interface.

An example

Developers code a control and label it, using a method initially defined  in HTML 4.1 (1999). i.e. it has been a conforming standard method for 15 years. They have done the right thing.

<label>email <input type="text"></label>

Browsers have implemented accessibility support for this method. The accessible name for the input element in the example is exposed by browsers via platform accessibility APIs. In testing conducted in 2012, all browsers that implemented accessibility support exposed the information correctly. They have done the right thing.

All of the assistive technology tested announced the correct label text. They have done the right thing.

Buggy is buggy regardless of source – no free pass

Browser vendors who do not implement standardized accessibility support and developers who do not code for accessibility are called out (regularly). Assistive technology vendors whose products do not convey information to users, provided using standardized coding patterns and exposed via standardized accessibility interfaces, are broken and must be fixed. They are doing the wrong thing.

Say Cheese!

Sep. 5th, 2014 06:20 pm
[syndicated profile] kirkus_kidlit_feed
Know any budding young photographers? There are two new children’s books on shelves, both which happen to be from Candlewick Press (which means they’re well-designed), aimed at young readers interested in learning more about photography and its history.

Animals Full of Life

Sep. 4th, 2014 07:27 pm
[syndicated profile] kirkus_kidlit_feed
I’ve heard more than one person say lately—because I like to read about picture books and about both those who make and those who appreciate them—that it’s hard to believe anyone would complain about the cost of a picture book. A price tag of, say, $17.99 might seem like a lot for a book, but as these people noted, in many instances you’re getting to see true works of art in the illustrated pages. (Many but not all instances, because let’s face it: Some illustrations are better than others.) Twenty bucks or so is rather a bargain for such an art gallery, one that a child can visit again and again. And, I might add, for those who can appreciate this but still can’t afford them, there’s always the local public library.
[syndicated profile] kirkus_kidlit_feed
You have a well-to-do neighbor who is perpetually, irritatingly sure that all is well-ordered in the great chain of being and that her privilege is deserved. You worry about her, but you worry more at the prospect that her child may grow up to be reflexively certain that the market will right all wrongs and the poor deserve to be so.
[syndicated profile] library_tech_jester_feed

Posted by Peter Murray

Receive DLTJ Thursday Threads:

by E-mail

by RSS

Delivered by FeedBurner

This weeks threads are a mixture of the future, the present and the past. Starting things off is A History of the Future in 100 Objects, a revealing look at what technology and society has in store for us. Parts of this resource are available freely on the website with the rest available as a $5 e-book. Next, in the present, is the decision by the Kuali Foundation to shift to a for-profit model and what it means for open source in the academic domain. And finally, a look at the past with the mindset list for the class of 2018 from Beloit College.

Feel free to send this to others you think might be interested in the topics. If you find these threads interesting and useful, you might want to add the Thursday Threads RSS Feed to your feed reader or subscribe to e-mail delivery using the form to the right. If you would like a more raw and immediate version of these types of stories, watch my Pinboard bookmarks (or subscribe to its feed in your feed reader). Items posted to are also sent out as tweets; you can follow me on Twitter. Comments and tips, as always, are welcome.

A History of the Future in 100 Objects

What are the 100 objects that future historians will pick to define our 21st century? A javelin thrown by an ‘enhanced’ Paralympian, far further than any normal human? Virtual reality interrogation equipment used by police forces? The world’s most expensive glass of water, mined from the moons of Mars? Or desire modification drugs that fuel a brand new religion?
A History of the Future in 100 Objects describes a hundred slices of the future of everything, spanning politics, technology, art, religion, and entertainment. Some of the objects are described by future historians; others through found materials, short stories, or dialogues. All come from a very real future.

I was turned on to this book-slash-website-slash-resource by a tweet from Herbert Von de Sompel:

— Herbert (@hvdsomp) August 21, 2014


The name is intriguing, right? I mean, A History of the Future in 100 Objects? What does it mean to have a “History of the Future”?

The answer is an intriguing book that places the reader in the year 2082 looking back at the previous 68 years. (Yes, if you are doing the math, the book starts with objects from 2014.) Whether it is high-tech gizmos or the impact of world events, the author makes a projection of what might happen by telling the brief story of an artifact. For those in the library arena, you want to read about the reading rooms of 2030, but I really suggest starting at the beginning and working your way through the vignettes from the book that the author has published on the website. There is a link in the header of each pages that points to e-book purchasing options.

Kuali Reboots Itself into a Commercial Entity

Despite the positioning that this change is about innovating into the next decade, there is much more to this change than might be apparent on the surface. The creation of a for-profit entity to “lead the development and ongoing support” and to enable “an additional path for investment to accelerate existing and create new Kuali products fundamentally moves Kuali away from the community source model. Member institutions will no longer have voting rights for Kuali projects but will instead be able to “sit on customer councils and will give feedback about design and priority”. Given such a transformative change to the underlying model, there are some big questions to address.

As Phil noted in yesterday’s post, Kuali is moving to a for-profit model, and it looks like it is motivated more by sustainability pressures than by some grand affirmative vision for the organization. There has been a long-term debate in higher education about the value of “community source,” which is a particular governance and funding model for open source projects. This debate is arguably one of the reasons why Indiana University left the Sakai Foundation (as I will get into later in this post). At the moment, Kuali is easily the most high-profile and well-funded project that still identifies itself as Community Source. The fact that this project, led by the single most vocal proponent for the Community Source model, is moving to a different model strongly suggests that Community Source has failed.
It’s worth taking some time to talk about why it has failed, because the story has implications for a wide range of open-licensed educational projects. For example, it is very relevant to my recent post on business models for Open Educational Resources (OER).

I touched on the cosmic shift in the direction of Kuali on DLTJ last week, but these two pieces from Phil Hill and Michael Feldstein on the e-Literate blog. I have certainly been a proponent of the open source method of building software and the need for sustainable open source software to develop a community around that software. But I can’t help but think there is more to this story than meets the eye: that there is something about a lack of faith by senior university administrators in having their own staff own the needs and issues of their institutions. Or maybe it has something to do with the high levels of fiscal commitment to elaborate “community source” governance structures. In thinking about what happened with Kuali, I can’t help but compare it to the reality of Project Hydra, where libraries participate with in-kind donations of staff time, travel expenses and good will to a self-governing organization that has only as much structure as it needs.

The 2018 Mindset List

Students heading into their first year of college this year were generally born in 1996.

Among those who have never been alive in their lifetime are Tupac Shakur, JonBenet Ramsey, Carl Sagan, and Tiny Tim.

On Parents’ Weekend, they may want to watch out in case Madonna shows up to see daughter Lourdes Maria Ciccone Leon or Sylvester Stallone comes to see daughter Sophia.

For students entering college this fall in the Class of 2018…

- 2018 List, by Tom McBride and Ron Nief, Beloit College Mindset List

So begins the annual “mindset list” — a tool originally developed to help the Beloit College instructors use cultural references that were relevant to the students entering their classrooms. I didn’t see as much buzz about it this year in my social circles, so I wanted to call it out (if for no other reason than to make you feel just a little older…).

[syndicated profile] library_tech_jester_feed

Posted by Peter Murray

Someone out there on the internet is repeatedly hitting this blog’s /xmlrpc.php service, probably looking to enumerate the user accounts on the blog as a precursor to a password scan (as described in Huge increase in WordPress xmlrpc.php POST requests at Sysadmins of the North). My access logs look like this:

176.227.196.86 - - [04/Sep/2014:02:18:19 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
195.154.136.19 - - [04/Sep/2014:02:18:19 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
176.227.196.86 - - [04/Sep/2014:02:18:19 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
176.227.196.86 - - [04/Sep/2014:02:18:21 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
176.227.196.86 - - [04/Sep/2014:02:18:22 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
176.227.196.86 - - [04/Sep/2014:02:18:24 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
195.154.136.19 - - [04/Sep/2014:02:18:24 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"
176.227.196.86 - - [04/Sep/2014:02:18:26 +0000] "POST /xmlrpc.php HTTP/1.0" 200 291 "-" "Mozilla/4.0 (compatible: MSIE 7.0; Windows NT 6.0)"

By itself, this is just annoying — but the real problem is that the PHP stack is getting invoked each time to deal with the request, and at several requests per second from different hosts this was putting quite a load on the server. I decided to fix the problem with a slight variation from what is suggested in the Sysadmins of the North blog post. This addition to the .htaccess file at the root level of my WordPress instance rejects the connection attempt at the Apache level rather than the PHP level:

RewriteCond %{REQUEST_URI} =/xmlrpc.php [NC]
RewriteCond %{HTTP_USER_AGENT} .*Mozilla\/4.0\ \(compatible:\ MSIE\ 7.0;\ Windows\ NT\ 6.0.*
RewriteRule .* - [F,L]

Which means:

  1. If the requested path is /xmlrpc.php, and
  2. you are sending this particular agent string, then
  3. send back a 403 error message and don’t bother processing any more Apache rewrite rules.

If you need to use this yourself, you might find that the HTTP_USER_AGENT string has changed. You can copy the user string from your Apache access logs, but remember to preface each space or each parenthesis with a backslash.

[syndicated profile] library_tech_jester_feed

Posted by Peter Murray

The conference organizers for WSSSPE2 have posted the list of accepted papers and the application for travel support. I was on the program committee for this year’s conference, and I can point to some papers that I think are particularly useful to libraries and the cultural heritage community in general:

[syndicated profile] alaskanlibrarian_feed

Posted by Daniel Cornwall

September is National Library Card signup month. I’d like to encourage every Alaskan who does not yet have a library card to go out and get one. Even if you hate books. Because the library is about so much more than books. Though we will always love readers and find them good reads.

If you live in Anchorage, visit http://libguides.anchoragelibrary.org/MyAccount to learn how to get your free library card. Aside from free access to books, music and videos from libraries stretching from Valdez to Juneau, you’ll get free access to:

 

If you live in Fairbanks, visit http://fnsblibrary.org/?page_id=74 to learn how you can get your library card. Aside from all the physical items you’d expect to find in a library system, your library card will give you access to:

 

If you live in Juneau, visit http://www.juneau.org/library/services_circulation.php to learn how a library card can be yours. This card will give you access to all the physical collections of the same system Anchorage is a part of, plus additional resources including:

 

If you live somewhere else in Alaska, check out the Alaska Library Association’s Library Directory. It contacts contact information for every known library in Alaska. The people at your local library can tell you how to get a library card and what good stuff comes with it.

Getting a library card is free and easy. It puts you in touch with a world of information and entertainment, much of which cannot be freely (or in some cases legally) accessed over the open web. What’s holding you back? Step out today and get yours today. Before the snow falls.

 

 


Filed under: alaska, libraries Tagged: library card month, library cards
Page generated Sep. 17th, 2014 03:31 pm
Powered by Dreamwidth Studios