Dear Stephen,
Our 'best practise' is option 1, so that the master digital file is an
exact representation of the entire artefact. We do in some cases store 2
copies of images, particularly if the image is small with a very large
border, the second copy can be a cropped version, but in some instances we
will re scan just the image without the border in order to meet the
required resolution.
Best wishes,
Becky
Rebecca Brumbill
Image Management Officer / Swyddog Rheoli Delweddau
Photography Department / Adran Ffotograffiaeth
Amgueddfa Cymru – National Museum Wales
Cardiff / Caerdydd
CF10 3NP
Tel / Ffon: 029 2057 3136
E-mail: [log in to unmask]
Please consider the environment before printing this email
Ystyriwch yr amgylchedd cyn argraffu'r e-bost hwn
On 09/01/2016 00:06, "Museums Computer Group on behalf of MCG automatic
digest system" <[log in to unmask] on behalf of [log in to unmask]>
wrote:
>There are 6 messages totaling 1264 lines in this issue.
>
>Topics of the day:
>
> 1. Digital Preservation of Stills: crop parameters (3)
> 2. Image Management Software
> 3. Call for papers: Eurographics Workshop on Graphics for Digital
>Fabrication
> (GraDiFab 2016)
> 4. Last day today - EVA London Conference 2016 deadline for proposals
> Friday 8th January 2016.
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>----------------------------------------------------------------------
>
>Date: Fri, 8 Jan 2016 10:00:58 +0000
>From: Stephen McConnachie <[log in to unmask]>
>Subject: Digital Preservation of Stills: crop parameters
>
>Hi everyone,
>
>I have a digital preservation question about crop parameters when
>scanning / photographing / storing photographic prints from a collection.
>
>At the BFI we're digitising our collection of photographic prints, it's a
>very large collection (over 1.5 million prints) and we want to get the
>scanning parameters right from the start of the project.
>
>There's some recommendation in the field to leave a small border around
>the edges of scanned artefact when cropping the digital preservation
>master. For example, the FADGI still image technical guidelines
>http://www.digitizationguidelines.gov/guidelines/FADGI_Still_Image_Tech_Gu
>idelines_2015-09-02_v4.pdf
>has this to say on page 64in the section called Cropping:
>We recommend the entire document be scanned, no cropping allowed. A small
>border should be visible around the entire document or photographic
>image. Careful placement of documents on flatbed scanners may require the
>originals to be away from platen edge to avoid cropping. For photographic
>records - If there is important information on a mount or in the border
>of a negative, then scan the entire mount and the entire negative
>including the full border. Notch codes in sheet film are often considered
>important to retain. Otherwise, scan photographs so there is only a small
>border around just the image area.
>
>However, a majority of our prints have a white border around the image,
>already. So in light of this recommendation: 'scan photographs so there
>is only a small border around just the image area' - I wanted to ask what
>crop parameters others in the sector are using for prints that contain a
>white border.
>
>I think the options are these:
>1. Black border around object
>a. Preservation master: crop leaving a border around the entire artefact,
>so the master consists of image and white border from the print, and
>black border from the capture process
>b. Access rendition(s): depending on preference / application, crop to
>remove the border, either at white border edge or to edge of image
>
>2. White border only
>a. Preservation master: crop to precise edge of artefact, so the master
>consists of image and white border only
>b. Access rendition(s): depending on preference / application, either
>reproduce as it is, to include the white border, or crop to edge of image
>
>3. Image only
>a. Preservation master: crop to precise edge of image, so the master
>consists of image only, without white or black border
>b. Access rendition(s): reproduce as it is
>
>I think it's probably safe to say that option 3 is too invasive, but I am
>really keen to hear from the sector if a consensus is clear on options 1
>or 2. I'd also like to learn whether cropping for access (to remove black
>border or even white border) is being done:
>a. on ingest to MAM systems (ie set rendition profiles to crop during
>creation of JPG derivative) or
>b. programmatically in application level (ie writing code to crop the src
>image for display in web browser / app / other)
>
>All the best,
>Stephen McConnachie,
>Head of Data, Collections & Information, BFI
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>------------------------------
>
>Date: Fri, 8 Jan 2016 10:25:43 +0000
>From: Danielle O'Donovan <[log in to unmask]>
>Subject: Re: Image Management Software
>
>Dear Graham and Sarah (and others who sent PMs too)
>
>THANK YOU SO MUCH.
>
>Sarah, I cannot answer those questions right now as our collections person
>is away till next week. You have asked ALL of the things our team need to
>think about.
>
>Graham, THANK YOU TOO. The actions you describe are all things we will
>need
>to do. I need to sit down with the team and work through your list.
>
>When I do have answers I will reply and am most grateful for your help in
>the meantime, you have just set the agenda for a long meeting!
>
>Yours,
>
>Danielle
>
>On 7 January 2016 at 15:45, Graham Sherwood <[log in to unmask]>
>wrote:
>
>> Hi Danielle,
>>
>> We've done a fair bit of research into just this sort of thing, not only
>> looking at the products out there but also installing them on our
>>servers
>> to see how they actually work. We have c.300,000 digital images at last
>> count and whole lot of positive and negative print archive. We use
>>images
>> not only for our reports but also print publications and online.
>>
>> Many organisations have digital assets and their criteria for
>> storing/locating images is often very similar.
>> Considerations:
>> - Take high resolution photos (raw + jpg) as required (have to
>>think
>> about what your end product is going to be)
>> - have an easier way for staff to view images, pdf resources,
>>rather
>> than trawling through folders.
>> - let users sort out images into collections/projects rather than
>> take copies of photos into their folders. (duplicating data)
>> - add metadata and associate these with each photo.
>> - Extract meta data from photos into reports
>> - search for photos easily by using specific keywords associated
>> with different media types
>> - share photos with all offices/company
>> - share photos privately and securely between clients
>> - preserve original images securely so they can’t be modified by
>> users e.g. by accident
>> - add other type of documents – posters, CAD drawings, pdf’s, text
>> documents etc.
>> - make it easier for the archive department to send photos to
>> deposition
>>
>> The type of software you asking about is a digital Asset Management
>>system
>> aka DAM's.
>>
>> DAM's typically have specific components
>> - a database which stores the metadata, file organisation and the
>> images (but not always)
>> - an interface which will be web based.
>>
>> There are several key things you have to be aware of all relating to
>>costs
>> and time
>>
>> You can either host it yourself or use a Cloud based
>>service/subscription
>>
>> If you are hosting it yourself
>> To have this system you need:
>> - A server with lots of digital storage
>> - A database server e.g. SQL or Oracle or MySQL
>> - A digital assets database product
>> - Staff tasked with cataloguing digital photos (usually a job in
>> itself)
>> - Around that the IT infrastructure to deal with
>>uploads/downloads,
>> users, networks etc.
>>
>> In the case of Cloud systems you need:
>> - everything above but it comes as part of a package and you pay
>>per
>> month/year.
>>
>> Typically you will be looking at something in the regions of c.£5,000
>>GBP
>>
>>
>> Some of the Digital Asset management systems we looked at and quite
>>liked
>> Asset Bank http://www.assetbank.co.uk/
>> Focus Open http://focusopen.com/
>> Resource Space http://www.resourcespace.org/index.php (open source
>> version available)
>> Extensis http://www.extensis.com/digital-asset-management/portfolio/
>>
>> Lots of others such as ibase, daydream, notre-dam, mosiacpics,
>>thirdlight.
>>
>> We quite liked Extensis because it could take our carefully organised
>> folder structure and make a system out of it.
>>
>> Feel free to ask me anything.
>>
>> , Graham
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Graham Sherwood
>> IT Manager
>> Pre-Construct Archaeology Ltd
>> Unit 54, Brockley Cross Business Centre, 96 Endwell Road, London SE4 2PD
>> Tel: 020 7639 9091
>> Direct: 020 7358 2191
>> Fax: 020 7639 9588
>> Mobile: 07775 645 701
>> [log in to unmask]
>> www.pre-construct.com
>>
>> -----Original Message-----
>> From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of
>> Danielle O'Donovan
>> Sent: 07 January 2016 10:22
>> To: [log in to unmask]
>> Subject: [MCG] Image Management Software
>>
>> Dear MCGers,
>>
>> I work for a historic house focused heritage charity, The Irish Heritage
>> Trust. This year we have expanded from operating out of two sites, one
>>in
>> Dublin and one in Cork, to four (Roscommon and Wexford).
>>
>> We work on Microsoft and will soon be using Office in the cloud or
>>similar.
>> We have thousands of images, of both collection items and of events held
>> in the houses. We need a way of cataloguing them for quick access by the
>> central Dublin team and by the staff at other sites. It would be purely
>>for
>> internal use and the main intention is that it will make it easier for
>> staff to find the image they need for print or web use.
>>
>> I'm at a loss to work out what system we should use to do this. Ideally
>> it would all be cloud based so we can all access it from anywhere. It
>>might
>> be useful to have some basic editing functions, just so that things can
>>be
>> cropped and saved for web before they go online.
>>
>> This email may have left people with more questions than answers so
>>please
>> point those out too!
>>
>> HELP!
>>
>> Danielle
>>
>> --
>>
>> Dr Danielle O’Donovan
>> Curator of Learning and Digital Engagement Irish Heritage Trust
>> 11 Parnell Square
>> Dublin 1
>> T: +353 1 874 8030
>> M: 085 722 5648
>> E: [log in to unmask]
>> W: www.irishheritagetrust.ie
>>
>>
>>
>>
>>
>> Registered Charity No: 16848
>>
>> ****************************************************************
>> website: http://museumscomputergroup.org.uk/
>> Twitter: http://www.twitter.com/ukmcg
>> Facebook: http://www.facebook.com/museumscomputergroup
>> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>> ****************************************************************
>>
>> ****************************************************************
>> website: http://museumscomputergroup.org.uk/
>> Twitter: http://www.twitter.com/ukmcg
>> Facebook: http://www.facebook.com/museumscomputergroup
>> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>> ****************************************************************
>>
>
>
>
>--
>
>Dr Danielle O’Donovan
>Curator of Learning and Digital Engagement
>Irish Heritage Trust
>11 Parnell Square
>Dublin 1
>T: +353 1 874 8030
>M: 085 722 5648
>E: [log in to unmask]
>W: www.irishheritagetrust.ie
>
>
>
>
>
>Registered Charity No: 16848
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>------------------------------
>
>Date: Fri, 8 Jan 2016 10:27:56 +0000
>From: Matt Faber <[log in to unmask]>
>Subject: Re: Digital Preservation of Stills: crop parameters
>
>Hi Stephen,
>
>This is always a good question and you will no doubt receive a wide
>variety of differing answers. However, for my money, I would go for
>option 1 as the master file should be the capture of the object and not
>the image. You might also need to capture additional information such as
>a colour checker card which would be placed within the black surround.
>Only when you create an optimised surrogate should you consider cropping
>of any sort.
>
>Hope that helps but be prepared for lots of different answers,
>
>Matt
>
>
>Matt Faber ALPI
>Advisor – Digital Imaging
>P 0203 697 5872
>E [log in to unmask]
>S mattfaberjisc
>T www.twitter.com/jiscdigital
>One Castlepark, Tower Hill, Bristol, BS2 0JA
>
>jisc.ac.uk
>Jisc is a registered charity (number 1149740) and a company limited by
>guarantee which is registered in England under Company No. 5747339, VAT
>No. GB 882 5529 90. Jisc’s registered office is: One Castlepark, Tower
>Hill, Bristol, BS2 0JA. T 0203 697 5800. jisc.ac.uk
>
>
>-----Original Message-----
>From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of
>Stephen McConnachie
>Sent: 08 January 2016 10:01
>To: [log in to unmask]
>Subject: Digital Preservation of Stills: crop parameters
>
>Hi everyone,
>
>I have a digital preservation question about crop parameters when
>scanning / photographing / storing photographic prints from a collection.
>
>At the BFI we're digitising our collection of photographic prints, it's a
>very large collection (over 1.5 million prints) and we want to get the
>scanning parameters right from the start of the project.
>
>There's some recommendation in the field to leave a small border around
>the edges of scanned artefact when cropping the digital preservation
>master. For example, the FADGI still image technical guidelines
>http://www.digitizationguidelines.gov/guidelines/FADGI_Still_Image_Tech_Gu
>idelines_2015-09-02_v4.pdf
>has this to say on page 64in the section called Cropping:
>We recommend the entire document be scanned, no cropping allowed. A small
>border should be visible around the entire document or photographic
>image. Careful placement of documents on flatbed scanners may require the
>originals to be away from platen edge to avoid cropping. For photographic
>records - If there is important information on a mount or in the border
>of a negative, then scan the entire mount and the entire negative
>including the full border. Notch codes in sheet film are often considered
>important to retain. Otherwise, scan photographs so there is only a small
>border around just the image area.
>
>However, a majority of our prints have a white border around the image,
>already. So in light of this recommendation: 'scan photographs so there
>is only a small border around just the image area' - I wanted to ask what
>crop parameters others in the sector are using for prints that contain a
>white border.
>
>I think the options are these:
>1. Black border around object
>a. Preservation master: crop leaving a border around the entire artefact,
>so the master consists of image and white border from the print, and
>black border from the capture process b. Access rendition(s): depending
>on preference / application, crop to remove the border, either at white
>border edge or to edge of image
>
>2. White border only
>a. Preservation master: crop to precise edge of artefact, so the master
>consists of image and white border only b. Access rendition(s): depending
>on preference / application, either reproduce as it is, to include the
>white border, or crop to edge of image
>
>3. Image only
>a. Preservation master: crop to precise edge of image, so the master
>consists of image only, without white or black border b. Access
>rendition(s): reproduce as it is
>
>I think it's probably safe to say that option 3 is too invasive, but I am
>really keen to hear from the sector if a consensus is clear on options 1
>or 2. I'd also like to learn whether cropping for access (to remove black
>border or even white border) is being done:
>a. on ingest to MAM systems (ie set rendition profiles to crop during
>creation of JPG derivative) or b. programmatically in application level
>(ie writing code to crop the src image for display in web browser / app /
>other)
>
>All the best,
>Stephen McConnachie,
>Head of Data, Collections & Information, BFI
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>------------------------------
>
>Date: Fri, 8 Jan 2016 14:25:10 +0000
>From: Corinna Hattersley-Mitchell
><[log in to unmask]>
>Subject: Call for papers: Eurographics Workshop on Graphics for Digital
>Fabrication (GraDiFab 2016)
>
>Dear All
>
>Apologies for any cross posting.
>
>
>
>Call for Papers: Eurographics Workshop on Graphics for Digital
>Fabrication (GraDiFab 2016)
>Lisbon, May 8, 2016. Co-located with the 37th annual conference of the
>European Association for Computer Graphics.
>Workshop URL: http://www.gradifab.org/
>Submissions deadline: February 20, 2016
>
>** Aims and scope **
>Digital fabrication technologies comprise a combination of programmable
>digital tools, processes, materials and equipment which allow the
>creation of physical objects of complexities not achievable by
>traditional manufacturing processes. Computer graphics research is at the
>centre of these developments, as it provides the underlying technologies
>which allow creating, validating and processing the 3D shapes and
>textures to be fabricated. We invite paper submission from a wide range
>of researchers and experts investigating on the many aspects related to
>computer graphics and digital fabrication technologies. This research is
>expected to contribute towards the establishment of digital fabrication
>as a viable and effective option for the creation of the objects of the
>future.
>
>Topics include (but are not limited to) the following:
>- 3D acquisition for digital fabrication
>- Algorithms and design tools for digital fabrication
>- Analysis for digital fabrication
>- Computational architecture
>- Multi-material fabrication
>- Optimisation algorithms for 3D printing
>- Validation tools
>- Interactive techniques with fabricated objects
>- User applications
>
>The intended audience involves experts from a wide range of areas such as
>computer graphics, additive manufacturing, computer aided design,
>material engineering, human computer interaction as well as end users
>from a wide range of applications including medicine, biology,
>engineering, arts and architecture. Hence, papers will need to present
>innovative computer graphics content but also refer to other areas or
>applications where they have been, or are going to be, tested and
>evaluated.
>
>** Submission instructions **
>Submissions reporting new work or new ideas in a relevant research area
>should be no longer than 10 pages and should follow the EG guidelines:
>https://www.eg.org/index.php/publications/guidelines#WS_Authors
>
>Authors are encouraged to submit printable 3D models along with their
>submissions to demonstrate the application of their techniques and
>methods. It is expected physical replicas will be exhibited during the
>workshop to disseminate the research to the wider Eurographics audience.
>
>Submissions will be reviewed by the International Programme Committee
>with a minimum of three reviewers per paper. Successful submissions will
>be presented at the workshop. Furthermore, proceedings of the workshop
>will be published by EG Publishing in the EG Digital Library
>
>** Important dates **
>Paper submission: February 20th, 2016
>Paper notification: March 15th, 2016
>Camera-ready deadline: March 30th, 2016
>Workshop: May 8th, 2016
>
>
>Kind Regards,
>Nico Pietroni, Karina Rodriguez and Asla Sa
>Organisers of GraDiFab 2016
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>Corinna Hattersley-Mitchell
>PA to Prof David Arnold & Administrative Assistant to Cultural
>Informatics Research Group
>Tel: +44 (0)1273 641 617 Please note I have a new number
>Cultural Informatics website<http://culturalinformatics.org.uk/>
>
>Follow us [Twitter_bird_icon]
>@CultInformatics<https://twitter.com/CultInformatics>
>
>Please note that I am only in the office Wednesday, Thursday and Friday
>but do have access to emails on the other days.
>
>For any urgent queries outside these days please contact John Clinton
>([log in to unmask])
>
>PLEASE NOTE, WE HAVE A NEW ADDRESS:
>
>Cultural Informatics Research Group
>University of Brighton
>Room 805, Cockcroft building
>Lewes Road
>Brighton BN2 4GJ
>UK
>
>
>
>
>___________________________________________________________
>This email has been scanned by MessageLabs' Email Security
>System on behalf of the University of Brighton.
>For more information see http://www.brighton.ac.uk/is/spam/
>___________________________________________________________
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>
>------------------------------
>
>Date: Fri, 8 Jan 2016 14:35:39 +0000
>From: Eleanor Lisney <[log in to unmask]>
>Subject: Last day today - EVA London Conference 2016 deadline for
>proposals Friday 8th January 2016.
>
>[image: Electronic Visualisation and the Arts]
>
>
>
>
>*Venue: British Computer Society, Covent Garden, London WC2E 7HA
>www.eva-london.org <http://www.eva-london.org/>*
>
>
>
>
>
>
>*Held annually in July, EVA London is one of the international EVA
>conferences <http://www.eva-conferences.com> (Electronic Visualisation &
>the Arts). Its focus is on the development and application of
>visualisation technologies, including art, music, dance, theatre and the
>sciences.Tuesday 12th July - Thursday 14th July 2016 Apologies for
>cross
>postingNEW - "This year featuring a selection of the winners from The
>Lumen Prize 2015/6 in our exhibition, with thanks to Lumen Founder Carla
>Rapoport http://lumenprize.com/ <http://lumenprize.com/> " Make sure you
>get your proposals in today!!*
>*Proposing for EVA London 2016*
>
>Proposals may be for a paper, a paper with demo, a demonstration, a
>workshop, an exhibition, or a panel discussion.
>
>Your proposal should come under one of the conference themes
><http://www.eva-london.org/eva-london-2016/eva-london-2016/propose-and-aut
>hor>.
>
>
>*Summary proposals only, please!* Please submit *only a summary proposal,*
>up to one page (400 words) for selection. Your proposal must be submitted
>via the EasyChair website:
>https://easychair.org/conferences/?conf=evalondon2016.
>
>The
>
>deadline for all proposals is *Friday 8th January 2016*. Demonstrations
>
>Demonstrations will be formally timetabled either as plenary sessions or
>in
>parallel with paper presentation sessions. Proposals are invited and
>should
>be submitted in outline as for papers, above. However, we will not expect
>detailed demo proposals until nearer the conference, to allow time for
>development. For publication you will be able to offer either a summary
>describing the demo or a paper.
>Panel sessions and workshops
>
>Proposals for panel sessions or workshops are welcome. A panel session
>would consist of two or more panel members who each make brief
>presentations or statements, followed by discussion with the audience. We
>will look for panel sessions to be of wide interest and to stimulate and
>engage the audience, since most delegates are interested and often expert
>in using and exploring technologies.
>
>
>Key Dates
>
>Please see Key Dates
><http://www.eva-london.org/eva-london-2016/eva-london-2016/key-dates>
>section for information on all deadlines.
>Questions?
>
>Please see Contacts <http://www.eva-london.org/contacts> if you have any
>questions.
>
>
>
>
>
>
>
>
>*Follow us onTwitter: @EVAlondonConf
><http://twitter.com/#%21/EVAlondonConf> Hashtag: #EVAlondonconfFacebook:
>EVA London <http://www.facebook.com/home.php?sk=group_204079106288985> *
>
>***********************************************************
>
>If this message was forwarded to you, join our mailing list to receive EVA
>London announcements (only) directly.
>Send an email to: [log in to unmask]
>Subject: leave blank.
>Message: SUBSCRIBE EVA-LONDON
>
>*EVA London **is co-sponsored by the **Computer Arts Society*
><http://www.computer-arts-society.org/>*, a Special Interest Group of
>the **British
>Computer Society* <http://www.bcs.org.uk/>*, and by the **BCS*
><http://www.bcs.org/>* .*
>
>***********************************************************
>
>*EVA Organising Committee*
>London South Bank University is a charity and a company limited by
>guarantee. Registered in England no. 986761. Registered Office: 103
>Borough
>Road, London SE1 0AA.
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>------------------------------
>
>Date: Fri, 8 Jan 2016 15:48:04 +0000
>From: James Morley <[log in to unmask]>
>Subject: Re: Digital Preservation of Stills: crop parameters
>
>Hi Stephen
>
>Everything that Matt said, with bells on! And that's coming from someone
>who deals with apis and creative end users who want a nice 'clean' image
>for display.
>
>A Friday afternoon thought - it's one of the (many) fantastic applications
>I see for IIIF technology. You would store e.g.
>http://iiif.embedr.eu/europeana___90402__RP_F_2011_49/full/full/0/native.j
>pg
>but with a few modified url parameters you can immediately get e.g.
>http://iiif.embedr.eu/europeana___90402__RP_F_2011_49/53,30,1668,2027/,100
>0/0/native.jpg
>(which is an interesting example itself for the notion of 'crop to edge of
>image'!). You don't even have to worry about fixing orientation as IIIF
>can
>handle that. And don't worry that in this case the 'master' appears to be
>a
>jpg, IIIF can work from lossless formats as well.
>
>Image source: https://www.rijksmuseum.nl/nl/collectie/RP-F-2011-49
>uploaded
>to Europeana at
>http://www.europeana.eu/portal/record/90402/RP_F_2011_49.html then
>accessed
>via the Europeana API to create
>http://embedr.eu/europeana___90402__RP_F_2011_49/ !
>
>Cheers, James
>
>
>---
>James Morley
>Work: labs.europeana.eu / [log in to unmask]
>Personal: www.jamesmorley.net / @jamesinealing
>Also: www.whatsthatpicture.com / @PhotosOfThePast
>
>On 8 January 2016 at 10:27, Matt Faber <[log in to unmask]> wrote:
>
>> Hi Stephen,
>>
>> This is always a good question and you will no doubt receive a wide
>> variety of differing answers. However, for my money, I would go for
>>option
>> 1 as the master file should be the capture of the object and not the
>>image.
>> You might also need to capture additional information such as a colour
>> checker card which would be placed within the black surround. Only when
>>you
>> create an optimised surrogate should you consider cropping of any sort.
>>
>> Hope that helps but be prepared for lots of different answers,
>>
>> Matt
>>
>>
>> Matt Faber ALPI
>> Advisor – Digital Imaging
>> P 0203 697 5872
>> E [log in to unmask]
>> S mattfaberjisc
>> T www.twitter.com/jiscdigital
>> One Castlepark, Tower Hill, Bristol, BS2 0JA
>>
>> jisc.ac.uk
>> Jisc is a registered charity (number 1149740) and a company limited by
>> guarantee which is registered in England under Company No. 5747339, VAT
>>No.
>> GB 882 5529 90. Jisc’s registered office is: One Castlepark, Tower Hill,
>> Bristol, BS2 0JA. T 0203 697 5800. jisc.ac.uk
>>
>>
>> -----Original Message-----
>> From: Museums Computer Group [mailto:[log in to unmask]] On Behalf Of
>> Stephen McConnachie
>> Sent: 08 January 2016 10:01
>> To: [log in to unmask]
>> Subject: Digital Preservation of Stills: crop parameters
>>
>> Hi everyone,
>>
>> I have a digital preservation question about crop parameters when
>>scanning
>> / photographing / storing photographic prints from a collection.
>>
>> At the BFI we're digitising our collection of photographic prints, it's
>>a
>> very large collection (over 1.5 million prints) and we want to get the
>> scanning parameters right from the start of the project.
>>
>> There's some recommendation in the field to leave a small border around
>> the edges of scanned artefact when cropping the digital preservation
>> master. For example, the FADGI still image technical guidelines
>>
>>http://www.digitizationguidelines.gov/guidelines/FADGI_Still_Image_Tech_G
>>uidelines_2015-09-02_v4.pdf
>> has this to say on page 64in the section called Cropping:
>> We recommend the entire document be scanned, no cropping allowed. A
>>small
>> border should be visible around the entire document or photographic
>>image.
>> Careful placement of documents on flatbed scanners may require the
>> originals to be away from platen edge to avoid cropping. For
>>photographic
>> records - If there is important information on a mount or in the border
>>of
>> a negative, then scan the entire mount and the entire negative including
>> the full border. Notch codes in sheet film are often considered
>>important
>> to retain. Otherwise, scan photographs so there is only a small border
>> around just the image area.
>>
>> However, a majority of our prints have a white border around the image,
>> already. So in light of this recommendation: 'scan photographs so there
>>is
>> only a small border around just the image area' - I wanted to ask what
>>crop
>> parameters others in the sector are using for prints that contain a
>>white
>> border.
>>
>> I think the options are these:
>> 1. Black border around object
>> a. Preservation master: crop leaving a border around the entire
>>artefact,
>> so the master consists of image and white border from the print, and
>>black
>> border from the capture process b. Access rendition(s): depending on
>> preference / application, crop to remove the border, either at white
>>border
>> edge or to edge of image
>>
>> 2. White border only
>> a. Preservation master: crop to precise edge of artefact, so the master
>> consists of image and white border only b. Access rendition(s):
>>depending
>> on preference / application, either reproduce as it is, to include the
>> white border, or crop to edge of image
>>
>> 3. Image only
>> a. Preservation master: crop to precise edge of image, so the master
>> consists of image only, without white or black border b. Access
>> rendition(s): reproduce as it is
>>
>> I think it's probably safe to say that option 3 is too invasive, but I
>>am
>> really keen to hear from the sector if a consensus is clear on options
>>1 or
>> 2. I'd also like to learn whether cropping for access (to remove black
>> border or even white border) is being done:
>> a. on ingest to MAM systems (ie set rendition profiles to crop during
>> creation of JPG derivative) or b. programmatically in application level
>>(ie
>> writing code to crop the src image for display in web browser / app /
>>other)
>>
>> All the best,
>> Stephen McConnachie,
>> Head of Data, Collections & Information, BFI
>>
>> ****************************************************************
>> website: http://museumscomputergroup.org.uk/
>> Twitter: http://www.twitter.com/ukmcg
>> Facebook: http://www.facebook.com/museumscomputergroup
>> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>> ****************************************************************
>>
>>
>> ****************************************************************
>> website: http://museumscomputergroup.org.uk/
>> Twitter: http://www.twitter.com/ukmcg
>> Facebook: http://www.facebook.com/museumscomputergroup
>> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>> ****************************************************************
>>
>
>****************************************************************
> website: http://museumscomputergroup.org.uk/
> Twitter: http://www.twitter.com/ukmcg
> Facebook: http://www.facebook.com/museumscomputergroup
> [un]subscribe: http://museumscomputergroup.org.uk/email-list/
>****************************************************************
>
>------------------------------
>
>End of MCG Digest - 7 Jan 2016 to 8 Jan 2016 (#2016-5)
>******************************************************
YMWADIAD
Mae pob neges ebost a anfonir i neu gan Amgueddfa Cymru yn cael ei
sganio gan systemau diogelwch awtomatig er mwyn rheoli negeseuon
digymell a dileu cynnwys amhriodol neu beryglus. Cafodd y neges hon ei
sganio am firysau cyn ei hanfon, ond dylech hefyd fodloni'ch hun bod y
neges, a phob atodiad ynddi, yn rhydd o firysau cyn ei defnyddio gan
nad yw'r Amgueddfa'n derbyn cyfrifoldeb am unrhyw golled neu ddifrod o
ganlyniad i agor y neges neu unrhyw atodiadau. Gall y neges hon ac
unrhyw ffeiliau a atodir ynddi gynnwys gwybodaeth gyfrinachol a
fwriadwyd ar gyfer y derbynnydd yn unig. Os ydych chi wedi derbyn y
neges trwy gamgymeriad, rhowch wybod i ni a chofiwch ddileu'r neges.
Safbwyntiau personol yr awdur yw'r safbwyntiau a fynegir yn y neges
hon, ac nid ydynt o reidrwydd yn cynrychioli safbwyntiau'r Amgueddfa.
Nid yw'r Amgueddfa'n atebol am unrhyw wallau, llygredd neu esgeulustod
a allai godi wrth drosglwyddo'r neges hon, felly na ddibynnwch ar y
cynnwys heb geisio cadarnhad ysgrifenedig yn gyntaf.
DISCLAIMER
Email to and from Amgueddfa Cymru - National Museum Wales is scanned
by automated security systems to control unsolicited messages and
eliminate inappropriate or dangerous content. This message was scanned
for viruses before transmission, but you should also satisfy yourself
that the message, and all attachments, are virus-free before use as
the Museum accepts no responsibility for any loss or damage that might
arise from opening the message or any attachments. This message and
any files transmitted with it may contain confidential information
intended only for the recipient. If you received it by mistake please
inform us and delete the message. The views expressed in this message
are the personal views of the author and may not necessarily represent
those of the Museum. The Museum accepts no liability for any errors,
corruption or omissions that might arise in transmission of this
message, so please do not rely on the contents without seeking
confirmation in writing.
--
Scanned by FuseMail.
****************************************************************
website: http://museumscomputergroup.org.uk/
Twitter: http://www.twitter.com/ukmcg
Facebook: http://www.facebook.com/museumscomputergroup
[un]subscribe: http://museumscomputergroup.org.uk/email-list/
****************************************************************
|
