[MCN-L] Call for PC members/reviewers & volunteers - VR/AR/MR (XR) & immersive learning IEEE technically co-sponsored conference
CALL FOR PROGRAM COMMITTEE MEMBERS/REVIEWERS AND CONFERENCE VOLUNTEERS iLRN 2020: 6th International Conference of the Immersive Learning Research Network June 21 to 25, 2020, Online and in Virtual Reality http://immersivelrn.org/ilrn2020 The 6th Annual International Conference of the Immersive Learning Research Network (iLRN 2020), the premier scholarly conference on the use of virtual reality (VR), augmented reality (AR), mixed reality (MR), and other related technologies (collectively known as "XR") for supporting education, training, and learning across sectors and contexts. This year, the conference will take place fully online using a number of virtual reality and other collaboration platforms. In addition to being an IEEE technically co-sponsored conference, the iLRN 2020 Virtual Conference is being organized in partnership with Educators in VR, who were behind the highly successful Educators in VR International Summit earlier this year that included over 170 speakers and attracted over 6,000 event participants from around the globe. We are expecting 8,000+ attendees at iLRN 2020! *** Program Committee Member / Reviewers Urgently Needed *** Due to the unexpectedly large volume of papers and proposals we have received, we are urgently calling for expressions of interest from suitably qualified and experienced individuals to join the Program Committee for the conference to help us review: - Academic Stream Work-in-progress papers - 2-4 pages for publication in proceedings - Practitioner Stream Oral presentation proposals - 1-2 pages, not published in proceedings - Practitioner Stream Poster presentation proposals - 1-2 pages, not published in proceedings - Workshop proposals - 2-3 pages, published in proceedings as extended-abstract descriptions of the session - Panel Session proposals - 2-3 pages, published in proceedings as extended-abstract descriptions of the session - Special Session proposals - 2-3 pages, published in proceedings as extended-abstract descriptions of the session If you are interested, please visit https://immersivelrn.org/ilrn2020/program-committee/ . Applications will be accepted on a rolling basis until all papers and proposals have been assigned. (Work-in-progress papers are due May 5, 2020; all other submission types are due May 18, 2020.) *** Conference Volunteer Opportunities *** A range of volunteer opportunities are available, including but not limited to conference internships for undergraduate and graduate students. Some of the roles we are looking to fill include: session chair/facilitator, moderator, audio-visual/technical support, virtual event greeter/usher, virtual event photographer, virtual event videographer/livestreamer, 2D artist / illustrator, 3D artist / modeler, graphic designer, documentation writer, presentation concierge, and general conference intern. See https://immersivelrn.org/ilrn2020/volunteer-opportunities . # PUBLICATION & INDEXING # All accepted and registered Academic Stream papers (including Work-in-progress) that are presented at the virtual conference, along with extended abstracts describing each of the Panel Sessions, Special Sessions, and Workshops that are presented, will be published in the conference proceedings and submitted to the IEEE Xplore(r) digital library. IEEE makes Xplore content available to its abstracting & indexing partners, including Elsevier (Scopus, Ei Compendex) and Clarivate Analytics (CPCI - part of Web of Science). # CONTACT # confere...@immersivelrn.org | ALBURY-WODONGA | BATHURST | BRISBANE | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA | LEGAL NOTICE This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with Charles Sturt University may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at Charles Sturt University. The views expressed in this email are not necessarily those of Charles Sturt University. Charles Sturt University in Australia The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Number: 5F (National)). TEQSA Provider Number: PV12018 Consider the environment before printing this email. ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network
[MCN-L] Final Call for Proposals/Papers: IEEE tech co-sponsored conference on XR & Immersive Learning
+ FINAL CALL FOR PAPERS AND PROPOSALS iLRN 2020: 6th International Conference of the Immersive Learning Research Network June 21-25, 2020, Online and in Virtual Reality Technically co-sponsored by the IEEE Education Society, with proceedings to be submitted for inclusion in IEEE Xplore(r) Conference theme: "Vision 20/20: Hindsight, Insight, and Foresight in XR and Immersive Learning" Conference website: http://immersivelrn.org/ilrn2020 + The 6th Annual International Conference of the Immersive Learning Research Network (iLRN 2020), the premier scholarly conference on the use of virtual reality (VR), augmented reality (AR), mixed reality (MR), and other related technologies (collectively known as "XR") for supporting education, training, and learning across sectors and contexts. This year, the conference will take place fully online using a number of virtual reality and other collaboration platforms. (Those without access to VR headsets can participate via desktop/laptop computer.) In addition to being an IEEE technically co-sponsored conference, the iLRN 2020 Virtual Conference is being organized in partnership with Educators in VR, who were behind the highly successful Educators in VR International Summit earlier this year that included over 170 speakers and attracted over 6,000 event participants from around the globe. We are expecting 8,000+ attendees at iLRN 2020! Following numerous requests and in consideration of the current global situation, we have re-opened the paper and proposal submission system and extended the deadlines for the following submission types. This will be the absolute final extension on the deadlines. - Academic Work-in-Progress papers for poster presentation (2-4 pages for publication in proceedings) - due May 5, 2020 - Academic Work-in-Progress papers for doctoral colloquium (2-4 pages for publication in proceedings) - due May 5, 2020 - Practitioner Stream oral and poster presentation proposals (1-2 pages, not published in proceedings) - due May 18, 2020 - Workshop, Panel Session, and Special Session proposals (2-3 pages, published in proceedings as extended-abstract descriptions of the sessions) - due May 18, 2020 Please see the conference website for paper and proposal templates and guidelines: https://immersivelrn.org/ilrn2020/call-for-papers-proposals/ # PUBLICATION & INDEXING # All accepted and registered Academic Stream papers (including Work-in-progress) that are presented at the virtual conference, along with extended abstracts describing each of the Panel Sessions, Special Sessions, and Workshops that are presented, will be published in the conference proceedings and submitted to the IEEE Xplore(r) digital library. IEEE makes Xplore content available to its abstracting & indexing partners, including Elsevier (Scopus, Ei Compendex) and Clarivate Analytics (CPCI - part of Web of Science). # CONTACT # confere...@immersivelrn.org | ALBURY-WODONGA | BATHURST | BRISBANE | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA | LEGAL NOTICE This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with Charles Sturt University may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at Charles Sturt University. The views expressed in this email are not necessarily those of Charles Sturt University. Charles Sturt University in Australia The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Number: 5F (National)). TEQSA Provider Number: PV12018 Consider the environment before printing this email. ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
[MCN-L] Mailing List
Please add me to your mailing list and the free educational website for contemporary diverse art and culture --- www.artura.org to your resources list -- Allan L. Edmunds President Brandywine Workshop and Archives 730 S. Broad Street Philadelphia, PA 19146 Office: 215.546.3675 Cell: 267.258.3558 Gallery: 267.831.2928 aedmu...@brandywineworkshop.com Websites: www.brandywineworkshopandarchives.org / www.artura.org Like us on Facebook www.facebook.com/BrandywineWorkshop Become a member of the Friends! ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] Looking for folks to help with an Animal Crossing MCN Proposal
Jeremy, I won't be able to attend MCN due to budget cuts but I did want to make sure you're aware of some Animal Crossing happenings in the science museum and aquarium world. The Monterey Bay Aquarium has been doing live Twitch streams of the game for a few weeks. We've been inviting guest experts onto the show to nerd out with us. It started with Emily Graslie of The Brain Scoop / Field Museum to talk fossils, with entomologist Ryan Gott of Phipps Conservatory, and Monday the 4th we'll be talking with a beetle expert from the Smithsonian. If anyone else has relevant expertise and is interested in meeting us in-game or joining the stream, please feel free to reach out to me. Check out recordings of our Animal Crossing streams here (we've done seven 2-hour episodes so far): https://www.twitch.tv/collections/B2eYd5CdAxZ8DA And read the story behind why we're doing this here: https://www.polygon.com/2020/4/13/21218993/animal-crossing-new-horizons-real-museum-curation-tour Best, Dana Allen-Greil Director of Digital Strategy Monterey Bay Aquarium ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] Guessable web URLs
Thanks all for the input. The main concern regarding access is meeting our legal obligation to rights holders, primarily for images of contemporary artwork. We will work with our copyright office to determine our risk strategy, but even with an open access model, we will need the ability to limit access to larger derivatives in certain cases. Separating the publishable vs. non-publishable images into separate directories makes perfect sense, it is figuring out some automation and management of the process that will be key (as Jeremy's comments address). I've lurked around the IIIF community for years, but the setup time/technical particulars have been a barrier in the past--perhaps it's time to reconsider. If we go that route, I'll surely be in touch with relevant folks for further advice. Thanks again, Emily. On Fri, May 1, 2020 at 12:23 PM Stefano Cossu wrote: > Emily, > I think others gave very valid suggestion that I mostly agree with, > especially about separating internal-use images with public ones. These > should reside in separate servers with clear firewall rules assigned. > Most importantly, you should isolate your internal management system > from the WWW. Assume your institution *will* (not *could*) be attacked > by malicious actors at any time. > > I support Jeremy's suggestion to look at IIIF. That takes some setup > time, as well as the need to produce specific derivatives. However, any > other image derivative is taken care of by the image server after that. > No need to manually generate thumbnail, web large/small/medium, etc. > > However, a IIIF manifest cannot enforce access to an image, it only > provides hints for good citizens about which derivatives they should > request. You can tackle restricted access in the same pipeline that > generates your IIIF-ready derivatives, by setting up a reduced > derivative size, or no public derivative at all, for > copyright-restricted images. This way you will have one folder / > repository with internal-only access behind firewall, and one open to > the WWW or behind the image server. > > This may sound like a lot to deal with, but in the long run it will > definitely save you a lot of management time, migration nightmares and > security loopholes. > > Stefano > > > On 5/1/20 10:41 AM, Jeremy Ottevanger wrote: > > Hi Emily, > > > > I'm going to leave for another thread the question of whether or not > > everything "should" be made available to the same degree - it's complex > > and not really what you're asking. But clearly that will be one element > > in people's assessment of whether the risk you're describing should be > > an issue or not. > > > > So, given that rights and licences are clearly important in your > > situation, would I think it a risk to leave a door ajar for people to > > take images you aren't meant to let them have? Well yes, it could be. Do > > I think people are likely to take them and abuse them? It's possible, of > > course, but perhaps it comes down the nature of the risks you want to > > avoid. If you could get into trouble with a rights holder that's one > > thing. But if you have an image licence sales team that is worried about > > lost revenue, I wouldn't worry so much. I don't think any commercial > > customer who is likely to have paid for a licence before is less likely > > to do so just because they figure out how to nick the image without > > paying. At the same time it can be a delicate political situation to get > > as far as you have and release any high-res images, in which case it can > > be canny politics to conspicuously avoid this risk. I've had to play > > this game in the past, even if I wanted to go much faster towards more > > open content, and in the end I believe it's really important to earn the > > trust of your organisation - it makes you a more plausible advocate for > > change anyway. > > > > So if there is a risk, what can you do to mitigate it? The obvious thing > > would be to put the images you want to publish into a separate directory > > to the ones you don't. That probably means having a second copy of them > > - that is surely the easiest solution. But if you can't do this for > > reasons of space (I hope not!) or of managing the process, I can think > > of a couple of other ways, although they could be equally tricky to > > automate or have other drawbacks. If this is a Linux server you could > > sim-link the published images to a location that you use for the web > > directory. Or you could do something clever with file permissions so > > that the web server (Apache or whatever) only has access to the > > published images (or with .htaccess). Both of these solutions could be > > automated, or semi-automated, for example by running a script over a > > list of files you want to sim-link. This might be built into the > > publication process. > > > > Or you could have a think about a IIIF solution (https://iiif.io/). > This > > has so many things going for it that go beyond what
Re: [MCN-L] Guessable web URLs
Emily, I think others gave very valid suggestion that I mostly agree with, especially about separating internal-use images with public ones. These should reside in separate servers with clear firewall rules assigned. Most importantly, you should isolate your internal management system from the WWW. Assume your institution *will* (not *could*) be attacked by malicious actors at any time. I support Jeremy's suggestion to look at IIIF. That takes some setup time, as well as the need to produce specific derivatives. However, any other image derivative is taken care of by the image server after that. No need to manually generate thumbnail, web large/small/medium, etc. However, a IIIF manifest cannot enforce access to an image, it only provides hints for good citizens about which derivatives they should request. You can tackle restricted access in the same pipeline that generates your IIIF-ready derivatives, by setting up a reduced derivative size, or no public derivative at all, for copyright-restricted images. This way you will have one folder / repository with internal-only access behind firewall, and one open to the WWW or behind the image server. This may sound like a lot to deal with, but in the long run it will definitely save you a lot of management time, migration nightmares and security loopholes. Stefano On 5/1/20 10:41 AM, Jeremy Ottevanger wrote: Hi Emily, I'm going to leave for another thread the question of whether or not everything "should" be made available to the same degree - it's complex and not really what you're asking. But clearly that will be one element in people's assessment of whether the risk you're describing should be an issue or not. So, given that rights and licences are clearly important in your situation, would I think it a risk to leave a door ajar for people to take images you aren't meant to let them have? Well yes, it could be. Do I think people are likely to take them and abuse them? It's possible, of course, but perhaps it comes down the nature of the risks you want to avoid. If you could get into trouble with a rights holder that's one thing. But if you have an image licence sales team that is worried about lost revenue, I wouldn't worry so much. I don't think any commercial customer who is likely to have paid for a licence before is less likely to do so just because they figure out how to nick the image without paying. At the same time it can be a delicate political situation to get as far as you have and release any high-res images, in which case it can be canny politics to conspicuously avoid this risk. I've had to play this game in the past, even if I wanted to go much faster towards more open content, and in the end I believe it's really important to earn the trust of your organisation - it makes you a more plausible advocate for change anyway. So if there is a risk, what can you do to mitigate it? The obvious thing would be to put the images you want to publish into a separate directory to the ones you don't. That probably means having a second copy of them - that is surely the easiest solution. But if you can't do this for reasons of space (I hope not!) or of managing the process, I can think of a couple of other ways, although they could be equally tricky to automate or have other drawbacks. If this is a Linux server you could sim-link the published images to a location that you use for the web directory. Or you could do something clever with file permissions so that the web server (Apache or whatever) only has access to the published images (or with .htaccess). Both of these solutions could be automated, or semi-automated, for example by running a script over a list of files you want to sim-link. This might be built into the publication process. Or you could have a think about a IIIF solution (https://iiif.io/). This has so many things going for it that go beyond what we're talking about here, but one salient point is that you aren't giving people direct access to a file - only the IIIF service on your server has access to the file, which it then does its magic on and sends out when requested. There is a manifest file containing information about the image, and if this isn't there then the IIIF service shouldn't return the image. I hope someone will correct me if I have that wrong! The downsides of IIIF would be that, firstly, you might not be publishing TIFFs like this, off the top of my head I'm not sure if that is supported by the spec or by any IIIF servers. And secondly, you'd need a way to publish manifests for each image you published. But once you did that you could have all the goodness that comes with IIIF and viewers like Mirador (https://projectmirador.org/) or Universal Viewer (https://universalviewer.io/) Good luck with your project, it's good to hear of more high resolution images being set free! All the best, Jeremy - Dr
Re: [MCN-L] Guessable web URLs
For what it's worth, systems like ContentDM present assets with guessable URLs too. So, I'm just pointing out that even those that have DAM systems this is an issue - whether they are aware of it or not. Joel Parham, MLIS JRP Consulting & Research, Inc. 310.923.4452 joel.par...@gmail.com On Fri, May 1, 2020 at 10:40 AM Emily Beliveau wrote: > Hi Sina, > > The way we're planning it, the media server will double as a storage > repository for all our media assets (masters and associated derivatives) so > everything will be in the same place in a predictable folder structure. We > only want to make some of the high-res images available for viewing or > download due to copyright. We could folder should-not-publish images > separately so they are not web accessible and can't be accessed by guessing > the URL, but in our current setup this would require manually moving files > around between web-accessible and non-web-accessible folders, and splitting > up the image sets for particular objects. Surely there is a better way, I'm > just hoping to find one that we can implement within the constraints of our > current IT environment, budget, and staff allocation. > > (I'm guessing this is a very junior-varsity question for the MCN group, but > this is where we are.) > > Emily. > > On Fri, May 1, 2020 at 10:31 AM Sina Bahram wrote: > > > Hi Emily, > > > > Just a high-level question, if I may, but if the resources are available > > for > > download, then is there a problem with having them be downloaded not > > through > > your search page? This seems like a feature, not a bug, IMHO. > > > > Take care, > > Sina > > > > President, Prime Access Consulting, Inc. > > Phone: 919-345-3832 > > https://www.PAC.bz > > Twitter: @SinaBahram > > Personal Website: https://www.sinabahram.com > > > > -Original Message- > > From: mcn-l On Behalf Of Emily Beliveau > > Sent: Friday, May 1, 2020 11:22 AM > > To: mcn-l@mcn.edu > > Subject: [MCN-L] Guessable web URLs > > > > Hi all (and attn: DAM and IP SIG members particularly) > > > > We are setting up a new media server that will allow us to provide > high-res > > image downloads via our collections search site for the first time > > (previously only small derivatives were web-accessible and our .tifs were > > stored elsewhere). We can control the publish-to-web status of each level > > of image derivative with our collections management system, but since all > > the high-resolution files will be on the same server, the URLs for all > > images (regardless of rights/publish status) will be guessable. > > > > How is this commonly handled? For context, we do not have a DAMS and > manage > > all our files in folders manually. We currently have ~80K image assets. > I'd > > like to understand our options and whether the community views this as an > > issue or not. > > > > Thanks, > > Emily. > > > > *--* > > > > *Emily Beliveau* > > > > Collections Management Advisor (Humanities) > > > > University of Alberta Museums > > Ring House 1, University of Alberta > > Edmonton, AB T6G 2E1 > > T: 780-492-0776 > > ___ > > 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@mcn.edu > > > > To unsubscribe or change mcn-l delivery options visit: > > http://mcn.edu/mailman/listinfo/mcn-l > > > > The MCN-L archives can be found at: > > http://www.mail-archive.com/mcn-l@mcn.edu/ > > > > ___ > > 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@mcn.edu > > > > To unsubscribe or change mcn-l delivery options visit: > > http://mcn.edu/mailman/listinfo/mcn-l > > > > The MCN-L archives can be found at: > > http://www.mail-archive.com/mcn-l@mcn.edu/ > > > ___ > 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@mcn.edu > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/mcn-l@mcn.edu/ > ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] Guessable web URLs
If you're saying that you're setting up a system where images you don't want to be public are on a public server, you can be sure they will get out sooner or later. Probably more or less immediately, especially if you're not black belts in robots.txt fu. What is this system? -- Matt Morgan m...@concretecomputing.com On Fri, May 1, 2020, at 5:37 PM, Emily Beliveau wrote: > Hi Sina, > > The way we're planning it, the media server will double as a storage > repository for all our media assets (masters and associated derivatives) so > everything will be in the same place in a predictable folder structure. We > only want to make some of the high-res images available for viewing or > download due to copyright. We could folder should-not-publish images > separately so they are not web accessible and can't be accessed by guessing > the URL, but in our current setup this would require manually moving files > around between web-accessible and non-web-accessible folders, and splitting > up the image sets for particular objects. Surely there is a better way, I'm > just hoping to find one that we can implement within the constraints of our > current IT environment, budget, and staff allocation. > > (I'm guessing this is a very junior-varsity question for the MCN group, but > this is where we are.) > > Emily. > > On Fri, May 1, 2020 at 10:31 AM Sina Bahram wrote: > > > Hi Emily, > > > > Just a high-level question, if I may, but if the resources are available > > for > > download, then is there a problem with having them be downloaded not > > through > > your search page? This seems like a feature, not a bug, IMHO. > > > > Take care, > > Sina > > > > President, Prime Access Consulting, Inc. > > Phone: 919-345-3832 > > https://www.PAC.bz > > Twitter: @SinaBahram > > Personal Website: https://www.sinabahram.com > > > > -Original Message- > > From: mcn-l On Behalf Of Emily Beliveau > > Sent: Friday, May 1, 2020 11:22 AM > > To: mcn-l@mcn.edu > > Subject: [MCN-L] Guessable web URLs > > > > Hi all (and attn: DAM and IP SIG members particularly) > > > > We are setting up a new media server that will allow us to provide high-res > > image downloads via our collections search site for the first time > > (previously only small derivatives were web-accessible and our .tifs were > > stored elsewhere). We can control the publish-to-web status of each level > > of image derivative with our collections management system, but since all > > the high-resolution files will be on the same server, the URLs for all > > images (regardless of rights/publish status) will be guessable. > > > > How is this commonly handled? For context, we do not have a DAMS and manage > > all our files in folders manually. We currently have ~80K image assets. I'd > > like to understand our options and whether the community views this as an > > issue or not. > > > > Thanks, > > Emily. > > > > *--* > > > > *Emily Beliveau* > > > > Collections Management Advisor (Humanities) > > > > University of Alberta Museums > > Ring House 1, University of Alberta > > Edmonton, AB T6G 2E1 > > T: 780-492-0776 > > ___ > > 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@mcn.edu > > > > To unsubscribe or change mcn-l delivery options visit: > > http://mcn.edu/mailman/listinfo/mcn-l > > > > The MCN-L archives can be found at: > > http://www.mail-archive.com/mcn-l@mcn.edu/ > > > > ___ > > 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@mcn.edu > > > > To unsubscribe or change mcn-l delivery options visit: > > http://mcn.edu/mailman/listinfo/mcn-l > > > > The MCN-L archives can be found at: > > http://www.mail-archive.com/mcn-l@mcn.edu/ > > > ___ > 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@mcn.edu > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/mcn-l@mcn.edu/ > ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] Guessable web URLs
Hi Emily, I'm going to leave for another thread the question of whether or not everything "should" be made available to the same degree - it's complex and not really what you're asking. But clearly that will be one element in people's assessment of whether the risk you're describing should be an issue or not. So, given that rights and licences are clearly important in your situation, would I think it a risk to leave a door ajar for people to take images you aren't meant to let them have? Well yes, it could be. Do I think people are likely to take them and abuse them? It's possible, of course, but perhaps it comes down the nature of the risks you want to avoid. If you could get into trouble with a rights holder that's one thing. But if you have an image licence sales team that is worried about lost revenue, I wouldn't worry so much. I don't think any commercial customer who is likely to have paid for a licence before is less likely to do so just because they figure out how to nick the image without paying. At the same time it can be a delicate political situation to get as far as you have and release any high-res images, in which case it can be canny politics to conspicuously avoid this risk. I've had to play this game in the past, even if I wanted to go much faster towards more open content, and in the end I believe it's really important to earn the trust of your organisation - it makes you a more plausible advocate for change anyway. So if there is a risk, what can you do to mitigate it? The obvious thing would be to put the images you want to publish into a separate directory to the ones you don't. That probably means having a second copy of them - that is surely the easiest solution. But if you can't do this for reasons of space (I hope not!) or of managing the process, I can think of a couple of other ways, although they could be equally tricky to automate or have other drawbacks. If this is a Linux server you could sim-link the published images to a location that you use for the web directory. Or you could do something clever with file permissions so that the web server (Apache or whatever) only has access to the published images (or with .htaccess). Both of these solutions could be automated, or semi-automated, for example by running a script over a list of files you want to sim-link. This might be built into the publication process. Or you could have a think about a IIIF solution (https://iiif.io/). This has so many things going for it that go beyond what we're talking about here, but one salient point is that you aren't giving people direct access to a file - only the IIIF service on your server has access to the file, which it then does its magic on and sends out when requested. There is a manifest file containing information about the image, and if this isn't there then the IIIF service shouldn't return the image. I hope someone will correct me if I have that wrong! The downsides of IIIF would be that, firstly, you might not be publishing TIFFs like this, off the top of my head I'm not sure if that is supported by the spec or by any IIIF servers. And secondly, you'd need a way to publish manifests for each image you published. But once you did that you could have all the goodness that comes with IIIF and viewers like Mirador (https://projectmirador.org/) or Universal Viewer (https://universalviewer.io/) Good luck with your project, it's good to hear of more high resolution images being set free! All the best, Jeremy - Dr Jeremy Ottevanger Director, Sesamoid Consulting Limited t: +44(0)1787 475 487 m: +44(0)7865 887 887 e: jer...@ottevanger.co.uk w: https://sesamoidconsulting.co.uk/ twitter: @jottevanger LinkedIn: www.linkedin.com/in/jeremy-ottevanger On 01/05/2020 16:21, Emily Beliveau wrote: Hi all (and attn: DAM and IP SIG members particularly) We are setting up a new media server that will allow us to provide high-res image downloads via our collections search site for the first time (previously only small derivatives were web-accessible and our .tifs were stored elsewhere). We can control the publish-to-web status of each level of image derivative with our collections management system, but since all the high-resolution files will be on the same server, the URLs for all images (regardless of rights/publish status) will be guessable. How is this commonly handled? For context, we do not have a DAMS and manage all our files in folders manually. We currently have ~80K image assets. I'd like to understand our options and whether the community views this as an issue or not. Thanks, Emily. *--* *Emily Beliveau* Collections Management Advisor (Humanities) University of Alberta Museums Ring House 1, University of Alberta Edmonton, AB T6G 2E1 T: 780-492-0776 ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network
Re: [MCN-L] Guessable web URLs
Hi Sina, The way we're planning it, the media server will double as a storage repository for all our media assets (masters and associated derivatives) so everything will be in the same place in a predictable folder structure. We only want to make some of the high-res images available for viewing or download due to copyright. We could folder should-not-publish images separately so they are not web accessible and can't be accessed by guessing the URL, but in our current setup this would require manually moving files around between web-accessible and non-web-accessible folders, and splitting up the image sets for particular objects. Surely there is a better way, I'm just hoping to find one that we can implement within the constraints of our current IT environment, budget, and staff allocation. (I'm guessing this is a very junior-varsity question for the MCN group, but this is where we are.) Emily. On Fri, May 1, 2020 at 10:31 AM Sina Bahram wrote: > Hi Emily, > > Just a high-level question, if I may, but if the resources are available > for > download, then is there a problem with having them be downloaded not > through > your search page? This seems like a feature, not a bug, IMHO. > > Take care, > Sina > > President, Prime Access Consulting, Inc. > Phone: 919-345-3832 > https://www.PAC.bz > Twitter: @SinaBahram > Personal Website: https://www.sinabahram.com > > -Original Message- > From: mcn-l On Behalf Of Emily Beliveau > Sent: Friday, May 1, 2020 11:22 AM > To: mcn-l@mcn.edu > Subject: [MCN-L] Guessable web URLs > > Hi all (and attn: DAM and IP SIG members particularly) > > We are setting up a new media server that will allow us to provide high-res > image downloads via our collections search site for the first time > (previously only small derivatives were web-accessible and our .tifs were > stored elsewhere). We can control the publish-to-web status of each level > of image derivative with our collections management system, but since all > the high-resolution files will be on the same server, the URLs for all > images (regardless of rights/publish status) will be guessable. > > How is this commonly handled? For context, we do not have a DAMS and manage > all our files in folders manually. We currently have ~80K image assets. I'd > like to understand our options and whether the community views this as an > issue or not. > > Thanks, > Emily. > > *--* > > *Emily Beliveau* > > Collections Management Advisor (Humanities) > > University of Alberta Museums > Ring House 1, University of Alberta > Edmonton, AB T6G 2E1 > T: 780-492-0776 > ___ > 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@mcn.edu > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/mcn-l@mcn.edu/ > > ___ > 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@mcn.edu > > To unsubscribe or change mcn-l delivery options visit: > http://mcn.edu/mailman/listinfo/mcn-l > > The MCN-L archives can be found at: > http://www.mail-archive.com/mcn-l@mcn.edu/ > ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] Guessable web URLs
Hi Emily, Just a high-level question, if I may, but if the resources are available for download, then is there a problem with having them be downloaded not through your search page? This seems like a feature, not a bug, IMHO. Take care, Sina President, Prime Access Consulting, Inc. Phone: 919-345-3832 https://www.PAC.bz Twitter: @SinaBahram Personal Website: https://www.sinabahram.com -Original Message- From: mcn-l On Behalf Of Emily Beliveau Sent: Friday, May 1, 2020 11:22 AM To: mcn-l@mcn.edu Subject: [MCN-L] Guessable web URLs Hi all (and attn: DAM and IP SIG members particularly) We are setting up a new media server that will allow us to provide high-res image downloads via our collections search site for the first time (previously only small derivatives were web-accessible and our .tifs were stored elsewhere). We can control the publish-to-web status of each level of image derivative with our collections management system, but since all the high-resolution files will be on the same server, the URLs for all images (regardless of rights/publish status) will be guessable. How is this commonly handled? For context, we do not have a DAMS and manage all our files in folders manually. We currently have ~80K image assets. I'd like to understand our options and whether the community views this as an issue or not. Thanks, Emily. *--* *Emily Beliveau* Collections Management Advisor (Humanities) University of Alberta Museums Ring House 1, University of Alberta Edmonton, AB T6G 2E1 T: 780-492-0776 ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/ ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
[MCN-L] Guessable web URLs
Hi all (and attn: DAM and IP SIG members particularly) We are setting up a new media server that will allow us to provide high-res image downloads via our collections search site for the first time (previously only small derivatives were web-accessible and our .tifs were stored elsewhere). We can control the publish-to-web status of each level of image derivative with our collections management system, but since all the high-resolution files will be on the same server, the URLs for all images (regardless of rights/publish status) will be guessable. How is this commonly handled? For context, we do not have a DAMS and manage all our files in folders manually. We currently have ~80K image assets. I'd like to understand our options and whether the community views this as an issue or not. Thanks, Emily. *--* *Emily Beliveau* Collections Management Advisor (Humanities) University of Alberta Museums Ring House 1, University of Alberta Edmonton, AB T6G 2E1 T: 780-492-0776 ___ 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@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
