Friday, November 6, 2009

notes: Interaction & Evaluation

QUESTION: how are site mirrors updated to ensure sameness?


Ok, so somehow I managed to delete all my notes while updating. Great. Not doing them over.
Started with Arms and how usability means all factions of the DL, not just the user. Conceptual model, interface design, and functional design seem to make or break the success of the DL - if the DL is hard to navigate, or controls are hard to find or don't make sense, the user can get frustrated.


Middleware seems to consist of script that runs in browsers, or CGI on a server, to fulfill tasks that the user may not even realize are occurring.

Multimedia Information
Summarization
Sorting and categorization
Presentations
...these are all more important considerations to help the user easily determine if results are valid for their search. Especially with images and videos I think, as demonstrated by searching for stuff on youtube and coming up with homemade videos of unrelated garbage.

Kling and Elliott
I find it interesting that DL developers do not consider ease of use when designing DLs. Isn't that counterproductive? Isn't the whole point of a DL for people to use it?
5 models of typical computer designs are discussed

muddy point: preservation

No muddy point

Sunday, November 1, 2009

muddy point: access 2

Question: even if errors are found (Google books, badly scanned PDF) how much work is involved in fixing those errors? Once a PDF is created, is it possible to update one page within the file, or must the entire work be rescanned? If individual pages are individually linked as separate images this wouldn't be a problem, but for the PDFs I download, they are self-contained documents. Wouldn't it be less time/effort to more carefully review items before finalizing them, than to have to go back and re-digitize?