Football indexing: random note of UGH

So, indexing the Auburn 1975 game.  Guidelines say note every identifiable player.

Easiest players to identify: the ones standing on the sidelines. Numbers clear as newspaper print.  It’s those guys running and jumping and tackling who are tricky to see.  Oh well.

Hats off to the 2009 photographers who didn’t use deep field of vision on the camera, keeping the sidelines nice and fuzzy.

Football indexing: random note of UGH

LSU roster: Getting the word out

Sent an email, but covering bases.

The link for LSU’s roster at our rosters page reads:

I found this searching for Auburn’s roster, as well.

Per the disclaimer at the main page (, this is a fan site for the MEMPHIS Tigers (I was getting confused when the names didn’t match anyone at other rosters for Auburn). has some numbers (and good names).  I’ll keep an eye out.

LSU roster: Getting the word out

Random facts about Exif

Here are some facts about Exif, from the standards and elsewhere, that I will not be covering in tomorrow’s presentation, due to time, mostly:

  • There is an entire page in the standard dedicated to “equivalent expressions” of the verbs used in the standard.  For example, “shall” is equivalent to “is mandatory”.  I once had to revise an entire standards of dissertation formatting because I got tired of explaining to people that the “may” in “the student may follow these guidelines” was the same as the “may” in “the student may graduate”:  You don’t technically have to, but if you want your degree, you have to.
  • Great warning from the wiki page: “Photo manipulation software sometimes fails to update the embedded thumbnail after an editing operation, possibly causing the user to inadvertently publish compromising information.”  I want to add an ellipsis after “publish” and read the whole thing in a British accent:  “to inadvertently publish… compromising information.”  “You don’t say, Jeeves!  Aunt Agatha will go apoplectic when she sees that thumbnail!”
  • There is an element that lets computers know from which corner of the screen to start counting the rows and columns in an image.
  • Exif comments tend to be different than other image metadata comments because you start by declaring your character set.  Exif understands “ASCII”, “JIS”, and “Unicode”.  “JIS” is used in Japanese text, which makes sense, considering who made the standards.
  • There are elements which allow users to define exactly where the main subject is in the picture, by defining an invisible circle or rectangle around it.
  • The GPS elements for latitude and longitude use three rational numbers each (six whole numbers, each pair being the numerator and denominator) for the degrees, minutes, and seconds.  This means that, if the latitude is 34° 12′ 15″, then you can use 34/1, 12/1, 15/1.  However, if your GPS unit doesn’t use seconds, but decimal minutes, like 34° 12.25′, then you can say 34/1, 1225/100, 0/1.  It’s rather elegant.
  • Elements in INFO list blocks can be intriguing, especially the ones not used by Exif audio files.  There’s “archival location,” “medium,” “product” (what product the image was originally intended for).
  • There is a tag to let camera manufacturers note whatever they feel like noting.  The wiki article warns that, sometimes, the manufacturers are happy to encode that information.
Random facts about Exif

Notes on metadata presentations (in general)

A general post here.  Some notes on making a good online presentation.  Nothing too new here, and I’ll admit there’s a thin line between “good presentation rules” and “my personal pet peeves”.  I’ll also admit that I will not do half of these things next week.  Treat it like Bingo: What did Damen not do that he said to do?  Mark it off this list!

  1. If you can find a way to stand during your presentation, it’s a good thing.  Opens your diaphragm, allows you to move a bit, inserts some energy.  Give your headphones a lot of cord, get the monitor a bit higher than usual, and give it a go.
  2. If your slides make perfect sense to someone who hasn’t seen the presentation, then your slides are too wordy.  Handouts should make sense; your script (see below) should make sense.  The slides should let people know where you are in your presentation; it should possibly let them collect a central statement when they look later. Wordy slides grant the risk of making you a slide reader. Many people get frustrated when they know exactly what you’ll say before you say it for minute after minute.
  3. Fill your slide. Bigger text if needed. More pictures. If text is small, make more slides. If text is meant to be read after the presentation, put it in your handout.
  4. Speaking of, I believe links should go in a reference slide, if at all. If ALA didn’t have specific rules against it, I would, the next time I see a link in a presentation, run up and punch the screen, then say, “It’s broken.” Handouts are your friend, here.
  5. Some people are script people, some aren’t.  If you don’t know, then you are.  The ones who aren’t are those who KNOW that, if they read a script, they might as well be saying, “Bueller?  Bueller?”  Then again, that might be better than your improvised behavior.  Who knows?

So, there we have it. The EXIF presentation is still at the research stage. EXIF is beautifully… complex. I’m not even sure I could list all of the left-side elements in ten minutes. So I won’t.

Notes on metadata presentations (in general)

Remember, use that map!

Last night, I did a quick check, and I saw that 21 images were on the map.  This is just a reminder, since the map is kind of a “hidden element”: At some point, you’ll click on “Map” (two to the right of the “File” link), type in the name of the stadium (it may help to click on the stadium name in the schedule links to see the current name), and click “Find”.  It’ll put a pin on the Map link on the left.

For full info and screenshots, go to the Spatial Coverage element guidelines.

Remember, use that map!

Workflow management: A primer

So, again, the DAM Foundation article notes that a full DAM system has proper workflow management.  What is workflow management?

The Wikipedia article really is pretty clean on this.  You need a few components working together:

  1. Process tracking and management.  We all, at some point, have those forms with three or more signature blanks that basically say, “these people have done what they need to do with this.”  That’s process tracking.  The forms, though, don’t usually say what those people are doing, assuming that they know.  That has the hazard of creating knowledge depots: “Greg’s out, we can’t do this.  What about Gary?  He does the same thing, right?  He could, but he doesn’t know what Greg does on these.  Well, we’ll have Gary ask Greg when he comes back.”  And then Greg gets hit by a bus, and you make up another process without him, but that’s okay, Greg’s process was made up when Joe got hit by a bus (lots of killer buses in my office).  A WMS allows someone to say, “For these items, Jim does this, and then Jim decides which things Greg or Gary need to do from this pool of possible things, and we usually give it a week to get done.”
  2. Process automation.  Suppose Dave’s process is always “open this file, run this filter, save file as PNG”.  That’s macro-able, right?  You’ve got better things for Dave to do, right?  Please say yes.  Anyways, a WMS can work with other application’s automated capabilities to do certain things to assets without having a human do a certain exact thing over and over again.  And again, Jim can make the decision on what automatic things are needed for a certain item as his step.
  3. Complex project processes.  While Jim’s working, Team Delta needs to create these three files, send two to Team Bravo, and have those three files waiting for Peter when step five comes around.  Some of these processes border on project management.

Now, think of this.  Your team may not need all of these items in your DAM system.  Maybe your processes aren’t that automatable.  Maybe you need a more or less rigorous version control system to go along.  Maybe you expect to grow into a system.  You can see that DAM solutions should definitely be modular and possibly even from more than one manufacturer.  When we talk about these things, we moving a bit beyond software applications and more towards business solutions and systems.  Your decision on DAM may incorporate budget, ability to use open-source solutions, and changing needs.  But at least you’re getting a start on what you require and why you require it.

Workflow management: A primer