thanks...no worries
Marianne Weldon
Collections Manager
301 Thomas
Bryn Mawr College
101 North Merion Avenue
Bryn Mawr, PA 19010
office 610-526-5022
mweldon at brynmawr.edu
----- Original Message -----
From: mcn-l-requ...@mcn.edu
To: mcn-l at mcn.edu
Sent: Thursday, June 10, 2010 3:00:03 PM
Subject: mcn-l Digest, Vol 58, Issue 10
Send mcn-l mailing list submissions to
mcn-l at mcn.edu
To subscribe or unsubscribe via the World Wide Web, visit
http://toronto.mediatrope.com/mailman/listinfo/mcn-l
or, via email, send a message with subject or body 'help' to
mcn-l-request at mcn.edu
You can reach the person managing the list at
mcn-l-owner at mcn.edu
When replying, please edit your Subject line so it is more specific
than "Re: Contents of mcn-l digest..."
Today's Topics:
1. Call for Participation: iConference 2011 in Seattle (Paul Marty)
2. Re: image file names (Images)
3. Re: image file names (Oberoi, Shyam)
----------------------------------------------------------------------
Message: 1
Date: Wed, 9 Jun 2010 17:31:53 -0400
From: Paul Marty <ma...@fsu.edu>
Subject: [MCN-L] Call for Participation: iConference 2011 in Seattle
To: Museum Computer Network Listserv <mcn-l at mcn.edu>
Message-ID: <D666AE06-9E91-49B7-9F2F-FB422DEBD26B at fsu.edu>
Content-Type: text/plain; charset=iso-8859-1
Call for Participation: iConference 2011 An open conference sponsored by
Information Schools of North America, Europe, and Asia
Seattle, Washington, USA
February 8 - 11, 2011
http://www.ischools.org/iConference11/2011index/
***PAPER SUBMISSION DEADLINE: August 30, 2010***
Greetings to everyone interested in HCI and Information! Please forward to your
colleagues!
We invite you to participate in the sixth annual conference sponsored by the
iCaucus, a growing association of over 25 Schools, Faculties, and Colleges in
North America, Europe and Asia that focus on Information. The iConference
gathers researchers and professionals who share the goal of making a difference
through the study of people, information, and technology. Under the banner
"Inspiration - Integrity - Intrepidity" we seek to showcase diversity in
research interests and approaches, and demonstrate how the field creates
leadership and impact on a global scale.
The four days will include peer-reviewed papers, posters, and alternative
events. Also being organized is a Doctoral Student Colloquium and a Junior
Faculty & Postdoc Colloquium, popular venues at past iConferences. Papers and
poster abstracts will be published in the ACM Digital Library. The aim is to
build community and promote and share excellence in research on information
challenges and opportunities. We have identified cross-cutting themes: social
inclusion, context, materiality, personalization, memory. The 2011 iConference
should be an exceptional venue for sharing insights and collaborating with
others who share your passion and research interests. For more information on
the range of topics visit the iConference web site, which includes more detail
and paths to past iConferences. But do not feel constrained, this is a dynamic
field that you will help shape!
The conference will be held at Seattle's Renaissance Hotel. The local host is
the University of Washington Information School.
Timeline:
August 30, 2010: Papers, Poster Abstracts, Alternative Event proposals,
Preconference Workshops
November 1: Authors notified
December 1: Final versions submitted
Links and Contact Information:
* CFP: http://www.ischools.org/iConference11/participation/
* Conference: http://www.ischools.org/iConference11/2011index/
* iCaucus: http://www.ischools.org/site/
Conference Co-Chairs
* Harry Bruce, University of Washington
* Jonathan Grudin, Microsoft Research
Program and Papers Co-Chairs
* Karen E. Fisher, University of Washington
* Jens-Erik Mai, University of Toronto
Poster Co-Chairs
* Paul Dourish, University of California, Irvine
* Ping Zhang, Syracuse University
Alternative Events Co-Chairs
* Allison Druin, University of Maryland
* Andrea Forte, Drexel University
Doctoral Colloquium Co-Chairs
* Eliza Dresang, University of Washington
* Bonnie Nardi, University of California, Irvine
* Howard Rosenbaum, Indiana University, SLIS
Junior Faculty and Postdoc Colloquium Co-Chairs
* Eileen Abels, Drexel University
* Jack Carroll, The Pennsylvania State University
Program Committee
* Eileen Abels, Drexel University
* Alessandro Acquisti, Carnegie Mellon University
* Bill Aspray, University of Texas, Austin
* John Bertot, University of Maryland
* Harry Bruce, University of Washington
* Jenna Burrell, University of California, Berkeley
* Nadia Caidi, University of Toronto
* Jack Carroll, The Pennsylvania State University
* Coye Cheshire, University of California, Berkeley
* Andrew Clement, University of Toronto
* Chris Coward, University of Washington
* Ed Cutrell, Microsoft Corporation
* Paul Dourish, University of California, Irvine
* Eliza Dresang, University of Washington
* Allison Druin, University of Maryland
* Barbara Endicott-Popovsky, University of Washington
* Melanie Feinberg, University of Texas, Austin
* Andrew Fiore, University of California, Berkeley
* Andrea Forte, Drexel University
* Jonathan Furner, University of California, Los Angeles
* Maria Garrido, University of Washington
* Sean Goggins, Drexel University
* Elke Greifeneder, Humboldt-Universit?t zu Berlin
* Jacek Gwizdka, Rutgers, the State University of New Jersey
* Margaret Hedstrom, University of Michigan
* Julia Hersberger, University of North Carolina, Greensboro
* Jette Hyldegaard, Danish Royal School
* Steven J Jackson, University of Michigan
* Julie Kientz, University of Washington
* Paul Marty, Florida State University
* Eric Meyers, University of British Columbia
* Bonnie Nardi, University of California, Irvine
* Geoffrey Nunberg, University of California, Berkeley
* Megan Oakleaf, Syracuse University
* Tapan Parikh, University of California, Berkeley
* Matt Ratto, University of Toronto
* David Ribes, Georgetown
* Howard Rosenbaum, Indiana University, SLIS
* Araba Sey, University of Washington
* Ramesh Srinivasan, University of California, Los Angeles
* Andrea Tapia, The Pennsylvania State University
* Joe Tennis, University of Washington
* Andrea Wiggins, Syracuse University
* Kate Williams, University of Illinois
* Jacob Wobbrock, University of Washington
* Ping Zhang, Syracuse University
--------------
Paul F. Marty, Ph.D.
Associate Professor, School of Library and Information Studies
College of Communication and Information, Florida State University
240 Louis Shores Building, Tallahassee, FL 32306-2100
http://marty.ci.fsu.edu | marty at fsu.edu
------------------------------
Message: 2
Date: Thu, 10 Jun 2010 10:15:43 -0700
From: Images <ima...@vanartgallery.bc.ca>
Subject: Re: [MCN-L] image file names
To: Museum Computer Network Listserv <mcn-l at mcn.edu>
Message-ID: <C8366BCF.8163%Images at vanartgallery.bc.ca>
Content-Type: text/plain; charset="iso-8859-1"
Thank you to everyone else on the list who provided such helpful responses. One
last question which would strengthen our case for adopting a new naming system
- what are the inherent problems with using decimals in a file name?
On 6/9/10 9:56 AM, "Parsell, David" <david.parsell at yale.edu> wrote:
The Yale Center for British Art and the Yale University Art Gallery at Yale
University have moved away from using the accession# and its inherent problems
in favor of a naming convention derived from the objectID field in TMS, which
is just the sequential number field assigned by the database each time a new
object record is added to TMS.
I'm sure all the other collection management systems use a sequential numbering
system as well. This number is used by the collection management system to link
the appropriate records from other tables to the object record since the number
never changes.
The beauty of this system is its structure, which allows you to automate file
creation and retrieval by other programs other than TMS. Also, it allows you to
retain a link to the TMS object even though the accession# may change over time.
Besides needing a better image naming convention than the accession#, we
developed this structured naming convention for use with a recently installed
enterprise level DAM at Yale University. The structured image# allowed us to
develop software that automated the TMS and DAM ingest of new images.
Here is a breakdown of our image naming convention. I will supply further
details on request.
Museum - TMS module - objectID - index - image type . suffix
ba-obj-60395-0003-pub.tif YCBA example (we like the idea of a 4 digit
index)
ag-obj-4487-001-mas.tif YUAG example (Art Gallery is happy with a 3
digit index)
Museum is ba for YCBA and ag for Art Gallery.
TMS module can be obj for object or exb for exhibition module.
ObjectID is the sequential record# in the object table. The exhibitionID
sequential# is used for exb images.
Index allows us to have more than one image for an object using the naming
convention. The name is always the same, just the index and image type changes.
Image type; we make 3 versions of each image, master (mas), bar (color
corrected with bars), pub (color corrected and cropped).
Suffix is whatever the file type is.
The switch to the structured naming convention has tremendously increased our
productivity.
Identifying an image is as simple as querying TMS on the objectID carried in
the image name.
My only regret is that we didn't do this sooner.
David Parsell
Systems Manager
Yale Center for British Art
1080 Chapel Street
PO Box 208280
New Haven, CT 06520-8280
203 432-9603
david.parsell at yale.edu
-----Original Message-----
From: mcn-l-bounces at mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of
Richard Light
Sent: Wednesday, June 09, 2010 11:42 AM
To: Museum Computer Network Listserv
Subject: Re: [MCN-L] image file names
In message <AD775DE5635C2042BF1DCB7EED36A83B850A1D at jlm-net.jlm.local>,
Perian Sully <psully at magnes.org> writes
>
>Funnily enough, I was just about to draft up a file naming standards
>document and post it online. Other than some of the inherent
>difficulties with trying to align the digital filenames with the
>accession number (particularly when you don't have an accession number
>yet), what are some other arguments in favor of using a unique
>identifier instead of the accession number?
One obvious argument is that it allows a single image to feature more
than one object.
Richard Light
>-----Original Message-----
>From: mcn-l-bounces at mcn.edu [mailto:mcn-l-bounces at mcn.edu] On Behalf Of
>Images
>Sent: Tuesday, June 08, 2010 12:03 PM
>To: Museum Computer Network Listserv
>Subject: [MCN-L] image file names
>
>We're reviewing how we name our image files and I'm hoping that some of
>you may have worked through this same issue. Currently, we use our
>accession number, however as this contains periods it has been
>identified as potentially problematic. For example, accession # 42.3.11
>= VAG-42.3.11.jpg. One suggestion is to change the decimals to zeros but
>we are concerned that this makes the image file name difficult to read.
>Have any of you found a good solution to a problem like this? Any
>thoughts or samples of your naming structure would be most appreciated!
>
>thanks very much
>Danielle
>
>
>_______________________________________________
>You are currently subscribed to mcn-l, the listserv of the Museum
>Computer Network (http://www.mcn.edu)
>
>To post to this list, send messages to: mcn-l at mcn.edu
>
>To unsubscribe or change mcn-l delivery options visit:
>http://toronto.mediatrope.com/mailman/listinfo/mcn-l
>
>The MCN-L archives can be found at:
>http://toronto.mediatrope.com/pipermail/mcn-l/
>_______________________________________________
>You are currently subscribed to mcn-l, the listserv of the Museum
>Computer Network (http://www.mcn.edu)
>
>To post to this list, send messages to: mcn-l at mcn.edu
>
>To unsubscribe or change mcn-l delivery options visit:
>http://toronto.mediatrope.com/mailman/listinfo/mcn-l
>
>The MCN-L archives can be found at:
>http://toronto.mediatrope.com/pipermail/mcn-l/
>No virus found in this incoming message.
>Checked by AVG - www.avg.com
>Version: 9.0.829 / Virus Database: 271.1.1/2926 - Release Date:
>06/08/10 19:35:00
--
Richard Light
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer
Network (http://www.mcn.edu)
To post to this list, send messages to: mcn-l at mcn.edu
To unsubscribe or change mcn-l delivery options visit:
http://toronto.mediatrope.com/mailman/listinfo/mcn-l
The MCN-L archives can be found at:
http://toronto.mediatrope.com/pipermail/mcn-l/
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer
Network (http://www.mcn.edu)
To post to this list, send messages to: mcn-l at mcn.edu
To unsubscribe or change mcn-l delivery options visit:
http://toronto.mediatrope.com/mailman/listinfo/mcn-l
The MCN-L archives can be found at:
http://toronto.mediatrope.com/pipermail/mcn-l/
------------------------------
Message: 3
Date: Thu, 10 Jun 2010 13:44:40 -0400
From: "Oberoi, Shyam" <shyam.obe...@metmuseum.org>
Subject: Re: [MCN-L] image file names
To: Museum Computer Network Listserv <mcn-l at mcn.edu>
Message-ID:
<3E5A9B377729884CAB52AFA762BC9BB30112A2E0FD at
SMAILPRODBE.metmuseum.org>
Content-Type: text/plain; charset="iso-8859-1"
Here at the MMA we've also moved away from using accession numbers in image
filenames. Instead, new images are assigned a unique integer value and then
prefaced with some string to indicate the source / type (ex: DP = digital
photography, DT = digital transparency etc).
In our experience, using accession numbers as a naming convention, whether with
periods or dashes, is problematic. For instance, when we implemented our DAM
we ingested legacy image files which had been named using the accession number.
But when we tried to do an exact match on these files to the appropriate TMS
record, the success rate was around 60-70% (which given the amount of files you
have may be acceptable -- in our case it was not). The most common reasons for
this mismatch were extra or missing commas, dashes, periods, whitespace, etc in
the filename -- in other words, standard parts of an accession number.
Shyam Oberoi
Sr. Website Technology Manager
The Metropolitan Museum of Art
-----Original Message-----
From: mcn-l-bounces at mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of
Parsell, David
Sent: Wednesday, June 09, 2010 12:56 PM
To: Museum Computer Network Listserv
Subject: Re: [MCN-L] image file names - Yale University
The Yale Center for British Art and the Yale University Art Gallery at Yale
University have moved away from using the accession# and its inherent problems
in favor of a naming convention derived from the objectID field in TMS, which
is just the sequential number field assigned by the database each time a new
object record is added to TMS.
I'm sure all the other collection management systems use a sequential numbering
system as well. This number is used by the collection management system to link
the appropriate records from other tables to the object record since the number
never changes.
The beauty of this system is its structure, which allows you to automate file
creation and retrieval by other programs other than TMS. Also, it allows you to
retain a link to the TMS object even though the accession# may change over time.
Besides needing a better image naming convention than the accession#, we
developed this structured naming convention for use with a recently installed
enterprise level DAM at Yale University. The structured image# allowed us to
develop software that automated the TMS and DAM ingest of new images.
Here is a breakdown of our image naming convention. I will supply further
details on request.
Museum - TMS module - objectID - index - image type . suffix
ba-obj-60395-0003-pub.tif YCBA example (we like the idea of a 4 digit
index)
ag-obj-4487-001-mas.tif YUAG example (Art Gallery is happy with a 3
digit index)
Museum is ba for YCBA and ag for Art Gallery.
TMS module can be obj for object or exb for exhibition module.
ObjectID is the sequential record# in the object table. The exhibitionID
sequential# is used for exb images.
Index allows us to have more than one image for an object using the naming
convention. The name is always the same, just the index and image type changes.
Image type; we make 3 versions of each image, master (mas), bar (color
corrected with bars), pub (color corrected and cropped).
Suffix is whatever the file type is.
The switch to the structured naming convention has tremendously increased our
productivity.
Identifying an image is as simple as querying TMS on the objectID carried in
the image name.
My only regret is that we didn't do this sooner.
David Parsell
Systems Manager
Yale Center for British Art
1080 Chapel Street
PO Box 208280
New Haven, CT? 06520-8280
?
203 432-9603
david.parsell at yale.edu
-----Original Message-----
From: mcn-l-bounces at mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of
Richard Light
Sent: Wednesday, June 09, 2010 11:42 AM
To: Museum Computer Network Listserv
Subject: Re: [MCN-L] image file names
In message <AD775DE5635C2042BF1DCB7EED36A83B850A1D at jlm-net.jlm.local>,
Perian Sully <psully at magnes.org> writes
>
>Funnily enough, I was just about to draft up a file naming standards
>document and post it online. Other than some of the inherent
>difficulties with trying to align the digital filenames with the
>accession number (particularly when you don't have an accession number
>yet), what are some other arguments in favor of using a unique
>identifier instead of the accession number?
One obvious argument is that it allows a single image to feature more
than one object.
Richard Light
>-----Original Message-----
>From: mcn-l-bounces at mcn.edu [mailto:mcn-l-bounces at mcn.edu] On Behalf Of
>Images
>Sent: Tuesday, June 08, 2010 12:03 PM
>To: Museum Computer Network Listserv
>Subject: [MCN-L] image file names
>
>We're reviewing how we name our image files and I'm hoping that some of
>you may have worked through this same issue. Currently, we use our
>accession number, however as this contains periods it has been
>identified as potentially problematic. For example, accession # 42.3.11
>= VAG-42.3.11.jpg. One suggestion is to change the decimals to zeros but
>we are concerned that this makes the image file name difficult to read.
>Have any of you found a good solution to a problem like this? Any
>thoughts or samples of your naming structure would be most appreciated!
>
>thanks very much
>Danielle
>
>
>_______________________________________________
>You are currently subscribed to mcn-l, the listserv of the Museum
>Computer Network (http://www.mcn.edu)
>
>To post to this list, send messages to: mcn-l at mcn.edu
>
>To unsubscribe or change mcn-l delivery options visit:
>http://toronto.mediatrope.com/mailman/listinfo/mcn-l
>
>The MCN-L archives can be found at:
>http://toronto.mediatrope.com/pipermail/mcn-l/
>_______________________________________________
>You are currently subscribed to mcn-l, the listserv of the Museum
>Computer Network (http://www.mcn.edu)
>
>To post to this list, send messages to: mcn-l at mcn.edu
>
>To unsubscribe or change mcn-l delivery options visit:
>http://toronto.mediatrope.com/mailman/listinfo/mcn-l
>
>The MCN-L archives can be found at:
>http://toronto.mediatrope.com/pipermail/mcn-l/
>No virus found in this incoming message.
>Checked by AVG - www.avg.com
>Version: 9.0.829 / Virus Database: 271.1.1/2926 - Release Date:
>06/08/10 19:35:00
--
Richard Light
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer
Network (http://www.mcn.edu)
To post to this list, send messages to: mcn-l at mcn.edu
To unsubscribe or change mcn-l delivery options visit:
http://toronto.mediatrope.com/mailman/listinfo/mcn-l
The MCN-L archives can be found at:
http://toronto.mediatrope.com/pipermail/mcn-l/
_______________________________________________
You are currently subscribed to mcn-l, the listserv of the Museum Computer
Network (http://www.mcn.edu)
To post to this list, send messages to: mcn-l at mcn.edu
To unsubscribe or change mcn-l delivery options visit:
http://toronto.mediatrope.com/mailman/listinfo/mcn-l
The MCN-L archives can be found at:
http://toronto.mediatrope.com/pipermail/mcn-l/
------------------------------
_______________________________________________
mcn-l mailing list
mcn-l at mcn.edu
http://toronto.mediatrope.com/mailman/listinfo/mcn-l
End of mcn-l Digest, Vol 58, Issue 10
*************************************
