Digital-Collections


I have all these great ideas floating around in my head for our web pages at any moment in time. Some of them are hilarious, never-will-do, ideas; but sometimes, I see something and I think: that should be easy enough to create for our page(s), right? Isn’t it just code that needs to be massaged? If I can figure out how to tease it just right, it should fit nicely in with our pages.

Sticky footers were such a piece of code that looked simple enough to implement. It’s just a footer at the end of the page; it is always hanging out down there; and, no matter how long or short the page scrolls, it stays at the bottom. Basically, it is a reverse (or mirror,) of a header that run across the top all the way, with the main part centered in the page. I wanted to use sticky footers because I was moving to templates on the re-designed pages; when using templates, the height of the page can vary, but the elements on the page stay the same. Well, what sounds easy isn’t always as such, as I (again) found out when I started to re-design our web pages. When will I ever learn? Probably, maybe, hopefully never, because I’m having too much fun finding solutions to problems.

Let’s start at the beginning of my struggle, and that always begins with research. Most sticky footers that I have seen go all across the bottom of the page, like so:

example_1

Then, there are sticky footers that always show “at the bottom,” even when, technically, it isn’t the bottom of the page:

example_2

I didn’t want either of these, exactly. I wanted something that stayed at “THE” “VERY” bottom of the page, and something that didn’t go all across the bottom. Like:

example_3

Doing a Google search, brings Mr. Fait’s page up first. Here is the css code for sticky footers:

 

* {

margin: 0;

}

html, body {

height: 100%;

}

.wrapper {

min-height: 100%;

margin: 0 auto -155px; /* the bottom margin is the negative value of the footer’s height */

}

footer, .push {

height: 155px; /* ‘.push’ must be the same height as ‘footer’ */

}

 

/*

 

Sticky Footer by Ryan Fait

http://ryanfait.com/

 

*/

 

Placing this in a css document and saving it, or placing at the top of the html doc between <head></head> divs should give the effect wanted. That’s it! Everything should work…right? Not so fast, little grasshopper. I couldn’t get this code to work as easily as advertised. When this happens, one of the first things I do when I see a sample of code I like is to go into Firebug (this can either be built right in, as it is in Firefox, or it can be downloaded for most other browsers. This browser app working right in the browser to “show” the code/html/css used in the layout of the page. This little app is indispensable for web designers.) In this case, I am using Firefox, so, here it’s located on the top, left of the search box. It looks like a little bug, and might be grayed out:

Firebug

Looking at Firebug revealed that this was a very simple layout. I’m sure it works great with designers who have very simple pages. Alas, my pages are complex, and maybe, er…messy, even. Plus, I have over 35 pages I maintain. As it, luckily, turns out: there are several designers who devote pages to nothing but creating sticky footers. And after searching, and using Firebug to explore those pages, I came across this one:

 

/*

Sticky Footer Solution

by Steve Hatcher

http://stever.ca

http://www.cssstickyfooter.com

*/

 

* {margin:0;padding:0;}

 

/* must declare 0 margins on everything, also for main layout components use padding, not

vertical margins (top and bottom) to add spacing, else those margins get added to total height

and your footer gets pushed down a bit more, creating vertical scroll bars in the browser */

 

html, body {margin:0;}

 

.wrap {min-height: 100%;}

 

#main {overflow:auto;

padding-bottom: 5px;}  /* must be same height as the footer */

 

#footer {position: relative;

margin-top: -70px; /* negative value of footer height */

height: 70px;

clear:both;}

 

/*Opera Fix*/

body:before {/* thanks to Maleika (Kohoutec)*/

content:””;

margin:0;

float:left;

width:0;

margin-top:-32767px;/* thank you Erik J – negate effect of float*/

}

 

I liked this one a lot because the designer goes into explicit detail about how to incorporate this code and issues known to using it. Also, it had additional code for Opera and code for use on IE 6 and lower (although I didn’t use that part of the code, and anyone using IE 6, in my humble opinion, is a very sad potato, indeed.) However, the css document listed on this page still wasn’t enough for me. Firebug revealed that another css was also used (called finerstyle.css.) After I copied that css code and placed it in its own document, I finally made the code work exactly as I thought it would. Which, again, highlights the super power of Firebug. And why one should always investigate pages. That’s the great thing about the internet and Firebug. Working hand in hand, you can find what you need and how to use it. Having finally accomplished my perfect sticky footer, I turned my attention to building templates for the updated pages. I’ll discuss my adventures in templates next time. Until then, happy coding.

AdamsFamilyPapers

I continue to search digital collections of other university libraries to see the interesting things that they’re doing.  Each university has unique items to feature, so it doesn’t benefit every collection to be presented in the exact same way.  New and creative ways of displaying digital content at another institution might not necessarily be a good fit for our current collections, but they could help us think about possible projects to initiate in the future.

One feature I came across is only useful if you have multiple and different versions of a document.  The University of Maryland Digital Collections includes poems by the Baroness Elsa von Freytag-Loringhoven.  Each poem has between two and seven versions since she kept her original manuscripts as she worked from her first draft through to the final, finished poem.  They use a “Versioning Machine” which is an open source software that lets people view numbered line-by-line transcriptions of each version side-by-side for comparison.  http://www.lib.umd.edu/dcr/collections/EvFL-class/?pid=umd:2257

Besides being able to view digital images of the manuscripts, the transcriptions of those pages help a researcher see the step-by-step changes the author made.  It gives a person the ability to almost get inside the mind of the author from their first thoughts and throughout the creative process.  While this tool would not be useful for most collections, it’s a very good example of a creative way to provide specific viewing platforms for unique collections.

I work in a department that has very little IT support, and as web development is constantly in a state of change, I need to do my own research to stay ahead of the curve. One of the best free* sites to learn about all things related to web development is www.w3schools.com. Our department also has unlimited access to www.lynda.com, but that’s not available for some. Plus, www.lynda.com gets bogged down in lessons and tutorials which can go on for hours, when sometimes a quick brush-up or how-to is all that’s needed. This allows me to get right back into my web page and implement my new idea. The site w3schools has quick, clear, easily defined answers which allow me to explore within each development tool. It has both tutorials and reference lists for HTML, CSS, JavaScript, SQL, PHP, and JQuery. The site also includes a section on web certificates, and contains an interactive color picker. What am I talking about? This site is very interactive! Not only can you read about each tool/technique, but also with its sandboxing of examples, you can try out the tools for yourself and see live results. If that’s not enough to get you started, there are over a thousand examples to peruse in your own time. This website makes it so easy that a very beginner to an advanced web designer can utilize it to its greatest potential. Best of all, it is constantly being updated. A very active and knowledgeable forum rounds out the website, so when you are still confused about actions and code writing, answers are just a click away.

* to obtain Web Certificates from this site, there is a fee involved. All other resources are free.

w3s

As you can see, the site is very well laid-out and easy to navigate. Going into the HTML section:

w3s_html1

It’s kind of hard to see in this example, but on the left side menu, you have a step-by-step html guide (starting at the very basic and moving progressively to more advanced techniques,) to HTML. In the middle of the page, is examples, and a “Try It Yourself” button. When you click on the “Try It Yourself” button, it opens to the sandbox:

w3s_sb1

Entering new code in between the <h1></h1> tag, and clicking on See Results box:

w3s_sb2b

This makes learning intuitive and fun. Each sandbox page opens in it’s own window, so going back to where you were is as simple as closing the window. Let’s go back to the HTML page. Further down the HTML page, you can see:

w3s_html2

There are links to HTML examples, or take a HTML Quiz (more than likely to help one prepare for the Web Certification that the site provides.) Clicking on the HTML Tag Reference link takes you to:

w3s_html_tagref (2)

This is very handy, as it shows all the HTML tags and also which are new or not supported in HTML5. I find the references pages very helpful when I’m updating my pages, especially as I move over to HTML5. Again, you can then use the left vertical menu to go to the specific page your interested in (this one being HTML; the other reference pages match the tool you are exploring.)

I have only dipped into the very basics of the website. The thing with this particular website is that it can get overwhelming and/or addictive. There is so much useful information here that I find myself spending way too much time on it, getting distracted from my own work. In that way, it is like www.lynda.com, but then I do not have to sigh my way through parts of a tutorial that I don’t need. Here, I can jump around and fiddle on code until I feel I understand it completely. It’s not the only site available that offers tutorials and sandboxing, but www.w3schools.com is about as thorough a website on learning these tools that I have discovered.

Image-01

In the Iowa State University Library Digital Collections, we mainly have collections of things that we have digitized here at the library, including photographs, letters, diaries and various documents.  However, born digital content, such as web pages, have also been brought together in other library digital collections.  We continue to look at these other opportunities for possible growth of our own.

The Library of Congress Digital Collections has web archiving.  Keeping old versions of web pages can be an often overlooked task.  When a web site is updated, how the old one looked could be lost forever unless there’s a policy and process in place to save the old one for historical reasons.  Sometimes there might be a temporary web page up for an anniversary or special event and when it’s over, if it’s not saved, that information could be lost.  Sometimes the content might not be that important, but someday people might want to see what the first web page of a university or department looked like to compare how things have changed.  The decisions of what to save, how to save it and make it available can be difficult and could impact every department on campus now that everybody seems to have their own web pages.

Columbia University Libraries Digital Collections includes a Human Rights Web Archive. None of the content of these web sites comes from the university.  Instead, they bring together web sites from all over the world to create a searchable collection available for research.  This extends the mission of the library to provide information by going beyond simply providing the information that exists at the institution. They search the online world instead, in order to provide various resources together in one place.

Preserving an historical record of web content could seem like a monumental task with the creation and changing of web content increasing exponentially all the time.  The sooner that policy and procedures everywhere are implemented to deal with this, the better.

DC-01

I continue to look at other university library digital collections to see what they are doing that we are not.  It can be informative to see what other people have decided is important enough to include on their websites.  Even if we don’t end up using these ideas on our own website, it’s good to know not only what other creators of digital collections are doing, but to find out what the users are seeing when they visit these websites and therefore the expectations that they might have when visiting digital collections such as ours.

One way of finding out what users want and expect is to ask them.  On the home page of the University of South Carolina Libraries Digital Collections, there is a link for a usability survey.   It is a brief survey that helps to find out who is using the digital collections (faculty, staff, undergraduates, grad students, or others); how easy the collections are to navigate; what kinds of things users are looking for; and whether users are able to find what they’re looking for.  This kind of information could be very useful in making decisions about the future of our digital collections.

Personally, I’m not a big user of social media, but it seems to have become a part of most people’s lives to some degree.  The home page of Duke University Libraries Digital Collections has a prominently featured area for both Twitter and Facebook.  This would encourage visitors to post comments on either of these social media outlets about what they’ve found and enjoyed in the digital collections.  Doing this would publicize the various contents of the digital collections to all the friends and followers of each user, which would in turn spread the word about the existence of the variety of things in the digital collections much more widely than any advertising the library could do otherwise.

Screen capture from the University of Washington University Libraries Digital Collections homepage: http://digitalcollections.lib.washington.edu/

Screen capture from the University of Washington University Libraries Digital Collections homepage.

There are always so many things that could be done, but there’s never enough time to do them all.  Having more staff and resources could help to do more, and having more funding would help to provide those additional staff and resources.  Every library and university, public or private, is always trying to raise money. Usually a person is more likely to donate their money if they know that it will go to something that is specifically important to them.  The home page of the University of Washington Libraries Digital Collections has a red star highlighting a link to “Support Digital Initiatives,  Make a Gift.”  The link takes you directly to the university foundation and the current needs in the library digital initiatives fund.   People who visit the digital collections and find things that interest them might be more likely to donate their money if they see that it could easily go directly to benefiting this interest of theirs and not just some general university fund.

Not every good idea for one library is necessarily a good fit for every other library.  However, noticing what others are doing and seeing what reactions they get can be a good way to start a conversation locally about what we might want to do in the future.

I’ve spent most of my last few months working on a project for the new ISU Extension Collection. The basic layout sounds simple enough: create a timeline for the important dates that this particular collection focuses on. The dates were not too far apart: 1900-1924. I’ve have seen a lot of web pages that incorporated timelines and I was excited to add this new skill to my tools. I did an online search of “timelines,” and got a whole gamut of ideas and tools.  I also started to see a basic pattern to all these timelines:

 

tl0

Basic.

 

tl2

Step up.

 

More modern.

More modern.

 

High tech.

High tech.

Google also has a timeline program. It is very similar to the High Tech version, only with a light background. But, as with most of these programs, you need to upload your information and it gets stored their servers. What happens if something happens to that program in the future? Also, all of these options take up the whole webpage to display the timeline. I wanted a timeline that was incorporated into the rest of my page, a piece of a larger puzzle on the page.

I decided to get a little more creative and put a timeline on an actual image. I had the image already in hand. I just needed a part of that image turned into a timeline, while the rest of it linked to other pages. As it turns out, there is no easy way to create a timeline on image, (I suppose if you were a hardcore programmer with mad skills, you probably could knock one out.) I don’t consider myself a complete slouch when it comes to coding, but come on, it shouldn’t be that hard to make a timeline on a relatively straight, long image. I have a hard time believing I’m the first person who wants to do such a thing. Yet, with every link clicked, none of the code and options I came across showed me how to do this. I asked myself exactly what it was I wanted to do. Well, I reasoned that the closest thing I could think of was that I was trying to create a customizable popup, or mouseover or hover-over a place on an image. Searching for that, I found several javascript codes for making pop-ups over links and/or images, which looked pretty much like tooltips on steroids. Tooltip is an alt code you can put into your html to create an effect so that when you hover your mouse over an image or link, a little yellow box pops up after a short time, giving information.

ddtooltip

Example of tooltip code in action.

I have created tooltips for our drop-down menus to indicate who certain significant people are.  I have also created tooltips to give information about certain images on pages.

imgtooltip

After discovering that it might be possible to create tooltips for a timeline, I became a little more excited.  I’m not one to toot other people’s horns, but http://www.dynamicdrive.com/ has awesome, easy-to-use, customizable code. It’s all free, as long as you include their legal notice within your code. There are two other sources that I recommend for helping in creating web pages and learning programs: http://www.lynda.com/(NOTE: not a completely free site) and http://www.w3schools.com/(the best resource for html and css, with an added bonus of sandboxing to see effects). I cannot recommend these sites enough to help get you through common webpage issues.

So, here we go. Searching on the dynamicedrive.com site opened the door to some fantastic ideas to noodle on, but how could I get a timeline actually placed on the chosen image? What I ended up doing was way old school: I made an image map. However, I didn’t do it with Adobe Photoshop. I did it online with Easy Imagemap Generator (http://imagemap-generator.dariodomi.de). (Yes, that is actually its name… and yes, it is EASY.) You do, however, need to have Flash Player for this to work. After going to the webpage, there is an option to upload the image or insert the image link URL.

imgmpgn

Upon doing this, it automagically loads your image. Just click +Add Area and start clicking on the image, making boxes, circles, or polygons around the areas you want to create into links. There are also buttons on this page that are marked X Clear All, and Change Image. Every time you want a new linked area, just click on the +Add Area button and move back into the image to create a new linked area. Once you are done with with all your linked areas, you will notice the code text is displayed at the bottom.  You can have as many linked areas as you want; I believe I had around twenty linkable areas on my image.  This is a very basic example of the code text:

<img src=”url/to/your/image.jpg” alt=”” usemap=”#Map” />

<map name=”Map” id=”Map”>

<area alt=”” title=”” href=”#” shape=”poly” coords=”134,276,150,292,122,297,111,287,119,279″ />

[…]

</map>

This is the code you will need to put into your html to make the areas you created linkable for the mouse-over pop-up box. There are many things you can do with this code to create the kind of links you want. I just selected all this code and copied and pasted it over into my html following where my image was placed on the page.

Next, I headed over to dynamicdrive.com and clicked on “Links & Tooltips.” This took me to a page with several different snippets to experiment with. Notice how after the links, it lists the browser compatibility. Remember to test your code in different browsers anyway!  The one I used was suppose to work in FF, so when it didn’t, I knew I had a code error somewhere. Once I found the code I liked, I clicked on the link, and it took me to the actual code page. From there, it goes step-by-step through the process, even allowing downloading of necessary .js and .css files. My particular code did not need separate .css or .js files, so I just coped and pasted into my document. At the end of the code, there is typically a section on modifying the settings. All in all, it was a very easy way to get the code I wanted and place it in my webpage. My html code ended up looking something like this:

html-code

If you notice, since I am using an image map, I needed to tweak a few settings here and there to make the image map display the tooltip script correctly. The code I used on dynamicdrive.com was called “Cool DTML Tooltip II,” and what is there is slightly different from what I ended up using. Using it exactly as it is on that site resulted in no text popping up, even though the boxes themselves were appearing. It took me a while to figure out that i n order for the area shape to have the desired effect, I needed to put the area shape outside the ONMOUSEOVER code. (In other words, I couldn’t place it before the closing />.) Also, notice that my first area code is different from the second, and subsequent, codes. I had to do this in order for the desired effect to work in Firefox. I believe I had to do this because I had several clickable areas on one large image, instead of several smaller images all together.  Whatever the reason, I did get the effect to work in the end by altering the code in this way. I changed the color of the pop-up background and text size and style in the css. (The ddrivetip used “dhtmltooltip.”) Also, you can make the tooltip linkable. I did not do this for my timeline, but it is possible.

This is an example of the final results:

imagemap

In conclusion, I felt this was a better approach than the other official applications. It allowed me to customize the timeline to fit the needs of the project. It may not be a timeline in the strictest capacity, but I believe it satisfies the requirements for this particular collection.

1091map1As our regular readers know, the 1091 Project is a collaboration between Iowa State University Library and our conservation colleagues at Duke University Libraries. Well, this week, thanks to Kevin Driedger of the Library of Michigan, we have been participating in the 5 Days of Preservation project, a week-long collaboration among preservation professionals and institutions across the nation.  Kevin’s idea was simple but powerful: use social media to post a photo each day for five days of whatever preservation looks like for you that day.  Kevin then collected all those posted images in one place, the 5 Days of Preservation Tumblr blog. The collected photos showcase an impressive range of preservation activities that really illustrate the rich diversity of our  field.  So, this week, I encourage you not only to pop over to Preservation Underground for their 1091 post, but also to check out #5DaysOfPreservation, via Tumblr, Facebook, and/or Twitter. And kudos to Kevin for a fun and informative project!

Here is a quick recap of our ISU Library Conservation Lab posts for the week:

 

fb-LIFE

MONDAY: Preservation looked like this humidified and flattened Depression-era letter.

 

Nicole5Days

TUESDAY: Preservation looked like our student employee, Nicole, repairing books from the General Collection.

 

Photodoc5days-01

WEDNESDAY: Preservation looked like professional photography lamps set up in front of our magnetic wall for imaging large-format architectural drawings.

 

WikiLinks-5Days

THURSDAY: Preservation looked like committee work for the AIC Sustainability Committee. Melissa and her fellow committee members are performing their annual link maintenance this month on the sustainability pages of the AIC Conservation Wiki.

 

McCoy-Budget-5Days

FRIDAY: Preservation looked like Preservation Assistant Mindy working on the departmental budget (a *very* important part of preservation indeed!)

Next Page »

Follow

Get every new post delivered to your Inbox.

Join 872 other followers