Greetings!
It has been a long time, with many professional activities in between, but I'll soon be back in action covering some or all of a metadata MOOC by Coursera: Metadata: Organizing and Discovering Information. The course begins in July. It seems basic--my first choice was actually a Library Juice Academy metadata course that was dropped.
From this MOOC, I hope to get a better idea of the comparative landscape of metadata systems, and I will be paying specific attention to book and e-book metadata.
Wednesday, June 4, 2014
Tuesday, November 1, 2011
Cary Memorial Library Virtual Exhibit
The Edwin B. Worthen virtual exhibit at the Cary Memorial Library of Lexington, MA, has been published to the Interwebs!
The exhibit can be found here: Edwin B. Worthen Collection Virtual Exhibit
Here is a link to the WickedLocal article:
http://www.wickedlocal.com/lexington/features/x848573066/Cary-Library-digitizes-Lexington-historical-materials-in-Virtual-Exhibit#axzz1cTdmaZOc
I worked on this project, which was funded by a grant from the IMLS, from 1/2011-8/2011.
The exhibit can be found here: Edwin B. Worthen Collection Virtual Exhibit
Here is a link to the WickedLocal article:
http://www.wickedlocal.com/lexington/features/x848573066/Cary-Library-digitizes-Lexington-historical-materials-in-Virtual-Exhibit#axzz1cTdmaZOc
I worked on this project, which was funded by a grant from the IMLS, from 1/2011-8/2011.
Tuesday, October 25, 2011
Hiatus!
Hi all!
I been on a lengthy hiatus entitled "full-time fall semester with 2 jobs and an internship". Please pardon me. Fortunately, I have been engaged both in digital preservation and web design/information architecture, so I also have a lot to share. I fully intend to complete my excursion into 23 Things for Archivists, but during the semester it's not really feasible. Instead I am happy to share some of my digital preservation work here. I recently delved into the XENA software from the National Archives of Australia, and have included a brief report below (with an introduction to XENA). May you find it useful!
XENA
Besides being a leather-clad television warrior princess with a saucy blond sidekick, XENA, is also a digital preservation tool created by the National Archives of Austalia. XENA (XML Electronic Nomalising for Archives) is a free, open source software (yay!) it can be downloaded from Sourgeforge.net, bearer of all (okay, many) things open source! Download the National Archives of Australia XENA software at Sourceforge.net. XENA takes certain of your digital/media files and converts them to preservation-friendly formats (open source, well-supported, community-driven). It then wraps them in metadata and goodies to help render them in the future. The result is a .xena file that XENA will be able to open in the future, unlike your dusty old MS Powerpoints that you made in Windows 95 (and copyright, and copyright, and copyright, Microsoft).
Here's the rundown, from what I gathered:
PROS:
Report on Working with Xena
The above is a screen shot taken from plugin installation with XENA, with 2 failed conversions in the background. For a brief report, see below.
I been on a lengthy hiatus entitled "full-time fall semester with 2 jobs and an internship". Please pardon me. Fortunately, I have been engaged both in digital preservation and web design/information architecture, so I also have a lot to share. I fully intend to complete my excursion into 23 Things for Archivists, but during the semester it's not really feasible. Instead I am happy to share some of my digital preservation work here. I recently delved into the XENA software from the National Archives of Australia, and have included a brief report below (with an introduction to XENA). May you find it useful!
XENA
Besides being a leather-clad television warrior princess with a saucy blond sidekick, XENA, is also a digital preservation tool created by the National Archives of Austalia. XENA (XML Electronic Nomalising for Archives) is a free, open source software (yay!) it can be downloaded from Sourgeforge.net, bearer of all (okay, many) things open source! Download the National Archives of Australia XENA software at Sourceforge.net. XENA takes certain of your digital/media files and converts them to preservation-friendly formats (open source, well-supported, community-driven). It then wraps them in metadata and goodies to help render them in the future. The result is a .xena file that XENA will be able to open in the future, unlike your dusty old MS Powerpoints that you made in Windows 95 (and copyright, and copyright, and copyright, Microsoft).
Here's the rundown, from what I gathered:
PROS:
- Converts proprietary file formats to a limited number of open formats the ideas here being that:
- 1. Open formats have greater longevity and there will always be means to open them
- 2. Supporting fewer file formats is easier and cheaper for a repository.
- Fast and simple* (*once configured. I'll come back to that).
- Viewer is included with Xena
- Even though the original file is wrapped into an XML file, the reader will allow you to view what's in there).
- Files can be exported via the viewer.
- Unsupported files can still be binary normalised ("normalized", if you're not using The Queen's English :) ).
- You can still create a .xena file, but the file will not be normalized into a preservation-friendly format.
- The list of formats accepted by XENA is decently long, but still limited.
- Accepted formats can be found here: List of formats supported by XENA, by type
- *Installation and configuration can be a bit tricky.
- That was the asterisk above. The program is very easy to run, as long as it is configured properly. You'll want to read the documentation about configuration carefully.
- If not installing from Windows .zip file, other downloads are required.
- XENA uses several plug-ins to make the conversions successful. It needs Open Office for all downloads, and additional plugins if you're working from Mac OS or Linux. Again, make sure to read the documentation.
- There are some bugs.
- I had trouble converting MS Office applications from Windows XP, for example, which is a known issue. If you feel like reading my report, I talk about it down below. You can visit the Sourgeforge Bug Tracker for XENA or the Wiki of Known Issues with XENA on Sourceforge for more information.
- XENA supports .gzip, .jar, .tar, .zip, .mp3, .wav, .aiff, .ogg, .flac, .sql, .csv, .tsv, .ppt, .doc, .pps, .xsl, .xlsx, .pptx, .docx, .mpp, .rtf, .sylk, .sxc, .sxi, .sxw, .wpd, .pst, .trim, .bmp, .cur, .gif, .pcx, .psd, .ras, .svg, .tiff, .css, .xlst, and etc., etc., etc.... but who supports .xena!?
Report on Working with Xena
Sunday, August 28, 2011
Thing 16: Podcasts & Vodcasts
Hi all!
This Thing investigates the world of Pod/Vodcasts. Videos and audio recordings can be an excellent way to engage your users and to create interest in the collections of a repository. As you can see from my hackneyed first attempt, I rarely find myself in front of the camera. But, like anything else, practice does wonders to alleviate fears and encourage development. If, in the future, I find myself at a repository where I afforded the opportunity to showcase bits of collections internationally via Podcast/Vodcast, I would certainly accept the challenge enthusiastically.
Below is a video clip that I made as a brief introduction a project I am working on in the Wellesley Historical Society, in the affluent Massachusetts community whose name it bears. Like many archivists before me, I've been trapped in the basement for quite a while. Despite the preliminary stages of occupationally-induced asthma with which we are all so familiar, I have enjoyed having nearly-free reign over one of the largest storage spaces at the WHS. Under the supervision of the curator, I have been revamping the collection storage space, weeding, mitigating threats (pests, mold, temperature controls), and doing a lot of preservation work on town records, books, and volumes from personal collections and corporate bodies. Here's a glimpse:
Logistically, the inclusion of video material is relatively simple. If the primary target for a Vodcast is a blog on Blogger, the tools to embed the video in a particular post are accessible right from the "Compose" page. Videos can be created via webcam (this one was made using a laptop), or similar functionality on almost any standard digital camera. There are, of course, video cameras made expressly for that purpose, but, if your repository is planning only low-key presentations, there does not seem to be much call to invest in the heavier machinery. File conversion is likely necessary, especially for those working from PCs, and, specifically, those working in Windows. Videos created with Windows Media Player (probably the default for PC webcams) are not immediately compatible with Blogger, YouTube, and probably WordPress as well, though I have spent far less time working there, admittedly. The trickiest part of this extremely low-budg video, then, was file conversion. I went with a tool called WinFX Free Video Converter, which seems to have done the job quite nicely. I went through Geeky Dads Software. It's here, if anyone is interested:
WinFX Video Converter from Geeky Dads Software.
The creation of video material made on a weekly basis could rob an already-busy archivist of valuable time, true. The above video required multiple takes due to ringing phones and other distractions. It is also unedited. A repository establishing a video presence on Youtube or on its Blog would need to keep up regular posts to maintain interest and profile currency. Time for preparation and editing would also be required. It could turn out to be a major undertaking, especially if adopted as a series. The marketing value might trump the time requirement, though, if videos are used effectively. Perhaps a video series could be used to alleviate time spent on repetitive reference requests, for example, and would be well worth time spent developing it. I would certainly consider this as a regular undertaking in the future, given the opportunity!
This Thing investigates the world of Pod/Vodcasts. Videos and audio recordings can be an excellent way to engage your users and to create interest in the collections of a repository. As you can see from my hackneyed first attempt, I rarely find myself in front of the camera. But, like anything else, practice does wonders to alleviate fears and encourage development. If, in the future, I find myself at a repository where I afforded the opportunity to showcase bits of collections internationally via Podcast/Vodcast, I would certainly accept the challenge enthusiastically.
Below is a video clip that I made as a brief introduction a project I am working on in the Wellesley Historical Society, in the affluent Massachusetts community whose name it bears. Like many archivists before me, I've been trapped in the basement for quite a while. Despite the preliminary stages of occupationally-induced asthma with which we are all so familiar, I have enjoyed having nearly-free reign over one of the largest storage spaces at the WHS. Under the supervision of the curator, I have been revamping the collection storage space, weeding, mitigating threats (pests, mold, temperature controls), and doing a lot of preservation work on town records, books, and volumes from personal collections and corporate bodies. Here's a glimpse:
Logistically, the inclusion of video material is relatively simple. If the primary target for a Vodcast is a blog on Blogger, the tools to embed the video in a particular post are accessible right from the "Compose" page. Videos can be created via webcam (this one was made using a laptop), or similar functionality on almost any standard digital camera. There are, of course, video cameras made expressly for that purpose, but, if your repository is planning only low-key presentations, there does not seem to be much call to invest in the heavier machinery. File conversion is likely necessary, especially for those working from PCs, and, specifically, those working in Windows. Videos created with Windows Media Player (probably the default for PC webcams) are not immediately compatible with Blogger, YouTube, and probably WordPress as well, though I have spent far less time working there, admittedly. The trickiest part of this extremely low-budg video, then, was file conversion. I went with a tool called WinFX Free Video Converter, which seems to have done the job quite nicely. I went through Geeky Dads Software. It's here, if anyone is interested:
WinFX Video Converter from Geeky Dads Software.
The creation of video material made on a weekly basis could rob an already-busy archivist of valuable time, true. The above video required multiple takes due to ringing phones and other distractions. It is also unedited. A repository establishing a video presence on Youtube or on its Blog would need to keep up regular posts to maintain interest and profile currency. Time for preparation and editing would also be required. It could turn out to be a major undertaking, especially if adopted as a series. The marketing value might trump the time requirement, though, if videos are used effectively. Perhaps a video series could be used to alleviate time spent on repetitive reference requests, for example, and would be well worth time spent developing it. I would certainly consider this as a regular undertaking in the future, given the opportunity!
Wednesday, August 3, 2011
Thing 15: Widgets
Hi everyone!
Woohoo, widgets! Widgets are spectacularly useful. They're sort like the kid from the popular group that you invite to your party for status. With a widget, you can take information from one site (like your Twitter account, Facebook account, chat, or something else random), and place it in a different site. We actually already did this when we looked at Meebo, and I embedded the MeeboMe widget on the blog. [--->]
I've also got a counter on here, and a link to follow me on Twitter @Archivisitation.
From Twitter, you can install a widget that will display your most recent Tweets. This can be added to a site or to Facebook. It's a great way to get more of your repository's networking directly accessible from a single location (your site, Facebook page, etc.). Also from Twitter, you can add a widget that will search Tweets, one that will display your favorite Tweets, or one that will display your favorite followers. Any of these would be helpful for engaging folks into the online community of the repository. From Facebook, you can add a Profile Badge or a Page Badge to your site, and this will let people know that you have a presence on Facebook. It's definitely more noticeable than a link. If your repository is on LibraryThing, or your repository is part of a library that is, you can add a LibraryThing account widget that will display your favorite books, or a particular collection, or books with reviews. This widget would be a great way to get those staff recommendations out of the stacks and into your online community. The LibraryThing widget is also customizable. This 3jam widget allows users to send a message to a mobile account, without exposing the phone number. It could be helpful if your repository does text/SMS reference. This widget from del.icio.us allows you to display your new links-- which could connect users with related collections, other repositories, information about your or other archives, etc. Google has all sorts of widgets/"web elements" that can be tacked onto a site. The Maps widget could be helpful for pointing out the origination of a collection or document. ...And there are many more widget suggestions on Stan Shroeder's article, recommended by 23 Things.
These are another way to engage users and to make the archives visible. An invisible archives falls quickly by the wayside, and this technology is usually free, except for the cost of labor and upkeep. If your repository has the time and means (or, okay, realistically, can make the time or means), then networking can reap real, tangible benefits for your repository, staff, and patrons.
Woohoo, widgets! Widgets are spectacularly useful. They're sort like the kid from the popular group that you invite to your party for status. With a widget, you can take information from one site (like your Twitter account, Facebook account, chat, or something else random), and place it in a different site. We actually already did this when we looked at Meebo, and I embedded the MeeboMe widget on the blog. [--->]
I've also got a counter on here, and a link to follow me on Twitter @Archivisitation.
From Twitter, you can install a widget that will display your most recent Tweets. This can be added to a site or to Facebook. It's a great way to get more of your repository's networking directly accessible from a single location (your site, Facebook page, etc.). Also from Twitter, you can add a widget that will search Tweets, one that will display your favorite Tweets, or one that will display your favorite followers. Any of these would be helpful for engaging folks into the online community of the repository. From Facebook, you can add a Profile Badge or a Page Badge to your site, and this will let people know that you have a presence on Facebook. It's definitely more noticeable than a link. If your repository is on LibraryThing, or your repository is part of a library that is, you can add a LibraryThing account widget that will display your favorite books, or a particular collection, or books with reviews. This widget would be a great way to get those staff recommendations out of the stacks and into your online community. The LibraryThing widget is also customizable. This 3jam widget allows users to send a message to a mobile account, without exposing the phone number. It could be helpful if your repository does text/SMS reference. This widget from del.icio.us allows you to display your new links-- which could connect users with related collections, other repositories, information about your or other archives, etc. Google has all sorts of widgets/"web elements" that can be tacked onto a site. The Maps widget could be helpful for pointing out the origination of a collection or document. ...And there are many more widget suggestions on Stan Shroeder's article, recommended by 23 Things.
These are another way to engage users and to make the archives visible. An invisible archives falls quickly by the wayside, and this technology is usually free, except for the cost of labor and upkeep. If your repository has the time and means (or, okay, realistically, can make the time or means), then networking can reap real, tangible benefits for your repository, staff, and patrons.
Thing 14: Facebook Apps
Facebook: unpredictable, explosive, unavoidable? These can be positives and negatives. For a repository with an active Facebook page, Facebook apps can be a way to connect with users, or to create more interest in your archives/collections. The blog prompts from 23 Things for Archivists encouraged a discussion on the pluses and minuses of Facebooks apps, and there are many of each.
The advantages of installing apps on Facebook include increased visibility, low- or no-cost marketing (aside from the required time, of course), and creation of an involved community though social networking. Disadvantages come in that most apps require that you forfeit some control over personal information. Facebook may be given access to your Friends list (something you may seriously want to weigh as a repository respecting the privacy of its patrons). Some sneaky apps even require an acceptance of terms that can grant them access to your Friends' (or Fans', if you're a page) information as well. The best advice when app searching is to carefully read and weigh the permissions required to install that app. For an app to access the "personal information" of a repository's web page may not seem to create many negative consequences. Tracking may not seem ultra-threatening to a public institution account that is being responsibly used, either. However, an app that "requests" to access information about patrons ("Friends"/"Fans"/"Followers"), even their "Likes" or locations, could be potentially hazardous (or, at the very least, offensive) to those who trust your repository with information.
Facebook uses "personal" information and activity tracking, when allowed, to entice advertisers to give money in exchange for marketing information. The tracking, geolocating, etc., is used to create targeted advertising for a particular account. Again, for a repository, this might not seem very threatening. Some with personal accounts, however, might not want to subject their account information to analysis, whether the intent of that analysis be benign or malignant. ...It's still kind of creepy, even if it's just for advertising. What does this mean for your repository on Facebook? It means that when you "invite" a Friend/Follower/Fan to install an app, you may be inadvertently asking them to expose their information to third-party applications and sites. Many may be unwilling to do so, understandably, so don't be offended. Many, though, may be unaware of the consequences and particulars of installing apps (especially third-party apps) onto their Facebook accounts. If you'll be doing this regularly, make sure you know what's at stake, and make sure you are able to communicate the pros and cons to your patrons and "Friends".
One feature that can be really helpful to amalgamation and consolidation is importing a blog to a Facebook account. This can only be done for one other site (i.e. only a single blog can be imported). This feature allows you to import blog entries as Notes, automatically. To configure, click on "Notes" on your repository's profile, then scroll down to "Subscribe" (you may have to go into a particular note to access "Subscribe"). Click on "Edit Import Settings", and type in your blog's URL. Easy! Now your Friends can read what you post on the blog right on Facebook. One less step.
We talked about putting Meebo on Facebook in Thing 2... I blogged about it here. But, as Blogger user Norton enlightened me in the comment to that post, a single account can be on either Facebook Chat or Meebo (through Facebook), but not both simultaneously. But, Meebo or Twitter accounts can be linked on Facebook through apps listed in the "Utilities"section. Either or both of these, or a combination of other apps, could be very useful in consolidating different social media accounts. Under "Business" (perhaps one of the most relevant sections for a repository to explore), SlideShare or LinkedIn accounts can be added. Using these tools, an archives can make presentations about its collections and share them via Facebook, or connect with users who might solely use LinkedIn for professional networking. Definitely helpful. The Family Tree app (Utilities) might be a wonderful way to map out a collection created by a family, so that users can see all the players involved. Many interesting possibilities lend themselves to these apps.
Just be aware of the pros and cons of Facebook (I wrote some of my own perspective on this in Thing 6: Social Networking. Also, be aware that many of your users (or possibly even most, depending on your constituency) will not be on Facebook. This is also true of any or all of the other social networking avenues you may be traveling down with your repository. While consolidating on Facebook can be beneficial, be sure to not "put all your eggs in one basket" as it were. And PRIVACY SETTINGS, PRIVACY SETTINGS, PRIVACY SETTINGS! Note especially, as you bop around, that there is an "Info available through your Friends" section under "Apps, Games, and Websites". Make sure you watch out for inadvertently exposing the information of your followers.
But, other than that, happy apping. It can be a lot of fun and a great tool set.
The advantages of installing apps on Facebook include increased visibility, low- or no-cost marketing (aside from the required time, of course), and creation of an involved community though social networking. Disadvantages come in that most apps require that you forfeit some control over personal information. Facebook may be given access to your Friends list (something you may seriously want to weigh as a repository respecting the privacy of its patrons). Some sneaky apps even require an acceptance of terms that can grant them access to your Friends' (or Fans', if you're a page) information as well. The best advice when app searching is to carefully read and weigh the permissions required to install that app. For an app to access the "personal information" of a repository's web page may not seem to create many negative consequences. Tracking may not seem ultra-threatening to a public institution account that is being responsibly used, either. However, an app that "requests" to access information about patrons ("Friends"/"Fans"/"Followers"), even their "Likes" or locations, could be potentially hazardous (or, at the very least, offensive) to those who trust your repository with information.
Facebook uses "personal" information and activity tracking, when allowed, to entice advertisers to give money in exchange for marketing information. The tracking, geolocating, etc., is used to create targeted advertising for a particular account. Again, for a repository, this might not seem very threatening. Some with personal accounts, however, might not want to subject their account information to analysis, whether the intent of that analysis be benign or malignant. ...It's still kind of creepy, even if it's just for advertising. What does this mean for your repository on Facebook? It means that when you "invite" a Friend/Follower/Fan to install an app, you may be inadvertently asking them to expose their information to third-party applications and sites. Many may be unwilling to do so, understandably, so don't be offended. Many, though, may be unaware of the consequences and particulars of installing apps (especially third-party apps) onto their Facebook accounts. If you'll be doing this regularly, make sure you know what's at stake, and make sure you are able to communicate the pros and cons to your patrons and "Friends".
One feature that can be really helpful to amalgamation and consolidation is importing a blog to a Facebook account. This can only be done for one other site (i.e. only a single blog can be imported). This feature allows you to import blog entries as Notes, automatically. To configure, click on "Notes" on your repository's profile, then scroll down to "Subscribe" (you may have to go into a particular note to access "Subscribe"). Click on "Edit Import Settings", and type in your blog's URL. Easy! Now your Friends can read what you post on the blog right on Facebook. One less step.
We talked about putting Meebo on Facebook in Thing 2... I blogged about it here. But, as Blogger user Norton enlightened me in the comment to that post, a single account can be on either Facebook Chat or Meebo (through Facebook), but not both simultaneously. But, Meebo or Twitter accounts can be linked on Facebook through apps listed in the "Utilities"section. Either or both of these, or a combination of other apps, could be very useful in consolidating different social media accounts. Under "Business" (perhaps one of the most relevant sections for a repository to explore), SlideShare or LinkedIn accounts can be added. Using these tools, an archives can make presentations about its collections and share them via Facebook, or connect with users who might solely use LinkedIn for professional networking. Definitely helpful. The Family Tree app (Utilities) might be a wonderful way to map out a collection created by a family, so that users can see all the players involved. Many interesting possibilities lend themselves to these apps.
Just be aware of the pros and cons of Facebook (I wrote some of my own perspective on this in Thing 6: Social Networking. Also, be aware that many of your users (or possibly even most, depending on your constituency) will not be on Facebook. This is also true of any or all of the other social networking avenues you may be traveling down with your repository. While consolidating on Facebook can be beneficial, be sure to not "put all your eggs in one basket" as it were. And PRIVACY SETTINGS, PRIVACY SETTINGS, PRIVACY SETTINGS! Note especially, as you bop around, that there is an "Info available through your Friends" section under "Apps, Games, and Websites". Make sure you watch out for inadvertently exposing the information of your followers.
But, other than that, happy apping. It can be a lot of fun and a great tool set.
Tuesday, August 2, 2011
Thing 13: Image Generators/Mashups
Good Tuesday to you all,
Today we're exploring image generators, which can be mashups (although "mashups" are any of a number of different media spliced and reworked). Use of these tools is a fun way to "play" with your institution's holdings. The products can be marketing tools, and would also be a valuable way to engage younger users (especially with potentially fragile items that they might not have as much access to). A review of copyright and creative commons licensing is helpful here, but, hopefully, your repository has acquired full copyright with the acquisition of Collection X, and you can forward some limited unreserved rights to your constituents.
For purposes of mashing, 23 Things for Archivists recommends Big Huge Labs, which is a free service with many available features.
The mashup below comes from a photograph of Herb Brooks Arena in Lake Placid, New York. Lake Placid hosted the Winter Olympics in 1932 and 1980. This arena is famous as the venue for the 1980 "Miracle on Ice", where an inexperienced Team USA, comprised of college players and post-collegiate amateurs, upset the powerhouse gold-medal favorite Soviet national team in the medal round. Team USA went on to win the gold medal in this arena, after defeating Finland. The arena (and story) has since been featured in the film "Miracle", which stars Kurt Russell as the charismatic head coach for whom the rink is now named.
Today we're exploring image generators, which can be mashups (although "mashups" are any of a number of different media spliced and reworked). Use of these tools is a fun way to "play" with your institution's holdings. The products can be marketing tools, and would also be a valuable way to engage younger users (especially with potentially fragile items that they might not have as much access to). A review of copyright and creative commons licensing is helpful here, but, hopefully, your repository has acquired full copyright with the acquisition of Collection X, and you can forward some limited unreserved rights to your constituents.
For purposes of mashing, 23 Things for Archivists recommends Big Huge Labs, which is a free service with many available features.
The mashup below comes from a photograph of Herb Brooks Arena in Lake Placid, New York. Lake Placid hosted the Winter Olympics in 1932 and 1980. This arena is famous as the venue for the 1980 "Miracle on Ice", where an inexperienced Team USA, comprised of college players and post-collegiate amateurs, upset the powerhouse gold-medal favorite Soviet national team in the medal round. Team USA went on to win the gold medal in this arena, after defeating Finland. The arena (and story) has since been featured in the film "Miracle", which stars Kurt Russell as the charismatic head coach for whom the rink is now named.
It's obvious that, with a little imagination, this and other mashup tools could be a great way to grab attention for a repository. The Big Huge Labs site has many different features. Once an image is altered, also, it can be ordered. The Magazine Cover feature might be a great way to advertise a new exhibit at a particular archives! It's easy and fun, and definitely worth playing around with!
Happy morphing and mashing folks!
Bee
Subscribe to:
Posts (Atom)