Comment #1 on issue 2154 by [email protected]: Flikr photograph report
http://code.google.com/p/qubit-toolkit/issues/detail?id=2154
Workflow:
1.Archivist searches for images using "Identifier" and "or"
2.Creates list of identifiers.
3.Cut and paste relevant information.
Possible solution discussed during meeting for using ICA-AtoM:
1.Archivist searches using "id" and "or"
2.Gets list of selected images
3.Exports list and data is pulled into a report that is structured for
Flickr, and the related jpegs are uploaded to Flickr.
Here is a related note in an article on The Library of Congress Flickr
Pilot Project regarding uploads [Michelle Springer et al.,"For the Common
Good: The Library of Congress Flickr Pilot Project", October 30, 2008 (pg
8-9):
"A customized upload application was required. Fortunately, Flickr allows
access to its Web services through a public application programming
interface (API) in a variety of programming languages. Additionally, third
party developers have created software development kits that ease the use
of the API. Using the flickrj toolkit for java and marc4j (a MARC record
toolkit), an Information Technology Services (ITS) staff member developed a
specialized application to upload photos and implement the
MARC-to-title-and-description mapping.
Using identifying information from the catalog record and Flickr’s machine
tags, the upload application was able to store the association between each
Flickr photo and its source photo. Machine tags use a special syntax to
define extra information about a tag and take this form:
<namespace>:<predicate>=<value>. One machine tag was added containing an
identifier for the photo (based on its digital identifier/handle), and a
second machine tag put the identifier in the context of the Dublin Core
namespace (defining the identifier type used to express the first machine
tag). Here is an example of a machine tag combination:
dc:identifier=http://hdl.loc.gov/loc.pnp/ggbain.11317
xmlns:dc=http://purl.org/dc/elements/1.1/";
--
You received this message because you are subscribed to the Google Groups "Qubit
Toolkit Issues" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/qubit-issues?hl=en.
