![]() ![]() In Blackboard Ultra, you can upload files directly to the Course Content area from a hard drive or from cloud storage. Embedding PowerPoint – Want to embed PowerPoint using a shared link, however the share option “anyone with the link at Humber can access” does not work and results in an error message.This means some embedded HTML content breaks when migrating from Original to Ultra. HTML Content – “Add HTML” function not available in Ultra.Mashups: Flickr, SlideShare – Not Available in Ultra.For workarounds and estimated fix timelines please refer to the Blackboard Ultra Issues and Workarounds document. The result: A set of 339 images that contains all the photos I uploaded, with no duplicates, all accomplished without deleting any of the original uploads.īig thanks to Maël Clérambault, the author of Flickraw, for his excellent little library, and thanks to Flickr for providing this very nice set of API calls.The following are known issues with this feature in Blackboard Ultra. And once the tags were in place, the work in Flickr was quite straightforward. I could have actually done everything with the Ruby script (delete the duplicates, change the remaining images to publicly visible, and add them to the appropriate set), but wanted to do that via Flickr so I could see what was happening as I went. Public_photos = my_stream.find_all Īt this point, I could apply tags to all the photos in the two groups, and all the rest of the fiddling could be done through Flickr’s web tools:į(:photo_id => photo.id, I then split that list into the initial set of publicly visible photos, and the photos I’d uploaded after things got screwy and kept private (i.e., visible only to me): After authenticating (following the example on the Flickraw web site), I was able to use it to pull down a list of all the photos from “The boys next door” It turns out that Flickraw was indeed powerful, flexible, and easy to use. A little searching this time, however, turned up Flickraw, which uses some really nifty Ruby metaprogramming to essentially build the Ruby part of the API “on the fly”, ensuring that it will be complete and up-to-date all automagically! I’d poked a little with some Ruby Flickr libraries in the past, but none of them ever seemed very complete and they were always struggling to stay on top of Flickr’s changes and extensions to the API. They have a very rich API for accessing (and modifying) photos and their associated information (like tags), so if I could figure out how to use that I’d be golden. This would, however, be pretty straight forward in a script if I had all the data I needed, and this is where Flickr redeemed itself. If I could identify them, then deleting the duplicates and making the rest visible would be easy, but I didn’t have a clue how to find the duplicates using Flickr’s tools. All the pictures were on Flickr, but there was no good (i.e., automated) way to figure out which were the duplicates. The morning came, and it turned out that I really didn’t have a workable plan. ![]() Ugh.īecause it was late and I was in a hurry, I ended up just uploading the whole set (over several attempts), but marked them as private so people wouldn’t end up seeing two copies of that first group of images, figuring I’d sort things out in the morning. This time, however, it chose to upload them in a semi-random order, so then it died I had 80-ish photos scattered all across the show, which meant I couldn’t just delete the first K from the list and restart the upload. It almost always takes me several tries to get a large pool of photos uploaded, which is a pain, but not fatal. ![]() Flickr’s Uploadr is fine for small uploads, but tends to die consistently and unpleasantly when I have several hundred photos to upload, like those from Thursday’s opening of “The boys next door”, this year’s Morris Area High School one-act. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |