Hi, Media handling records are generally used for identification of an object, and we have created media handling records with jpeg files for that purpose. But is it appropriate for original digital artwork files to be media handling records? Or should they be archived outside of CollectionSpace?  Other examples: very large image files intended for print, or video files, etc.? We also wonder if CollectionSpace media handling has best practice with regard to file size. thanks, Willi Wolf and Alex Nowik

Willi, For reference, UC Berkeley stores large (~50Mb) original TIFF images in CollectionSpace. CollectionSpace usually creates smaller JPEG derivatives to use in the UI. However, the large originals are always available. To create the derivatives, CollectionSpace makes system calls to a utility named ImageMagick <https://imagemagick.org/index.php>. The larger the original image, the more resources (temp disk space and RAM) ImageMagick will need to create the derivatives. Therefore, you may need to make some configuration changes to your system if you plan on uploading large (again, ~50Mb) image files to CollectionSpace. If your original digital artwork files are non-image files, you can still use CollectionSpace to manage these files --you just won't see things like preview thumbnails in the UI. Finally, if you want/need more flexibility in how you manage your digital artwork files, you could consider using a DAM tool like Piction. For example, the UC Berkeley Art Museum and Pacific Film Archive uses both Piction and CollectionSpace to manage some of their image files. Hope that helps? I'm sure others will chime in with their comments as well. -Richard On Wed, May 19, 2021 at 7:37 AM <ww@williwolf.net> wrote: > Hi, > > Media handling records are generally used for identification of an object, > and we have created media handling records with jpeg files for that purpose. > > But is it appropriate for original digital artwork files to be media > handling records? Or should they be archived outside of CollectionSpace? > Other examples: very large image files intended for print, or video files, > etc.? > > We also wonder if CollectionSpace media handling has best practice with > regard to file size. > > thanks, > > Willi Wolf and Alex Nowik > _______________________________________________ > Talk mailing list -- talk@lists.collectionspace.org > To unsubscribe send an email to talk-leave@lists.collectionspace.org >

Willi, UC Berkeley (i.e. the Hearst Museum of Anthropology) also stores a limited set of other media formats, e.g. "video files". CSpace does not make "derivatives" for non-image media -- instead the original media is stored and a placeholder for the media type is shown in the UI. The Hearst currently stores audio files (both AIFF and MP3 files) and video files (as MP4). In order to make "playable" versions of the streaming media, separate lower-quality versions of the media were made outside cspace and uploaded to CSpace separately alongside the high-res archival versions. A bit of an effort, to be sure! These streaming files are rendered outside the regular CSpace frontend and backend via custom code. Here are a couple records from the Hearst Museum Blacklight Portal. Video example (nb: no sound!): https://portal.hearstmuseum.berkeley.edu/catalog/02c53343-061d-4fdc-afad-213387ddb737 Audio example (mp3): https://portal.hearstmuseum.berkeley.edu/catalog/3e246fc1-a4a0-4a81-8a16-d8b6d6e514f3 Regards, John On Wed, May 19, 2021 at 9:09 AM Richard Millet <richard.millet@berkeley.edu> wrote: > Willi, > > For reference, UC Berkeley stores large (~50Mb) original TIFF images in > CollectionSpace. CollectionSpace usually creates smaller JPEG > derivatives to use in the UI. However, the large originals are always > available. To create the derivatives, CollectionSpace makes system calls > to a utility named ImageMagick <https://imagemagick.org/index.php>. The > larger the original image, the more resources (temp disk space and RAM) > ImageMagick will need to create the derivatives. Therefore, you may need > to make some configuration changes to your system if you plan on uploading > large (again, ~50Mb) image files to CollectionSpace. > > If your original digital artwork files are non-image files, you can still > use CollectionSpace to manage these files --you just won't see things like > preview thumbnails in the UI. > > Finally, if you want/need more flexibility in how you manage your digital > artwork files, you could consider using a DAM tool like Piction. For > example, the UC Berkeley Art Museum and Pacific Film Archive uses both > Piction and CollectionSpace to manage some of their image files. > > Hope that helps? I'm sure others will chime in with their comments as > well. > > -Richard > > On Wed, May 19, 2021 at 7:37 AM <ww@williwolf.net> wrote: > >> Hi, >> >> Media handling records are generally used for identification of an >> object, and we have created media handling records with jpeg files for that >> purpose. >> >> But is it appropriate for original digital artwork files to be media >> handling records? Or should they be archived outside of CollectionSpace? >> Other examples: very large image files intended for print, or video files, >> etc.? >> >> We also wonder if CollectionSpace media handling has best practice with >> regard to file size. >> >> thanks, >> >> Willi Wolf and Alex Nowik >> _______________________________________________ >> Talk mailing list -- talk@lists.collectionspace.org >> To unsubscribe send an email to talk-leave@lists.collectionspace.org >> > _______________________________________________ > Talk mailing list -- talk@lists.collectionspace.org > To unsubscribe send an email to talk-leave@lists.collectionspace.org >

Thank you all, this is very helpful !!