Like everyone else the agency, I use Sharepoint pretty much every day. I use it primarily to post and share documents, and locate various pieces of OSL information.
I've always had trouble creating and editing documents using IE with my particular computer. Some kind of weird configuration issue. I usually work around the issue by downloading and uploading documents. This also allows me to continue to use FireFox, which I really prefer to do. The other reason I like to use this method is I find that documents created in Sharepoint take a really long time to open ... documents created in Word and then uploaded don't seem to have the same problem.
I think it is too bad that OSL doesn't use more of Sharepoint's features ... I think discussion forums are particularly under used. Maybe if each committee committed to conducting at least part of their discussion via Sharepoint, we would end up with a lot fewer meetings! Just an idea ...
I also use Sharepoint to update the Oregon.gov web site for Library Support. This is probably my least favorite web editing platform that I've worked with in my career, but at least I have figured out how to do the basics.
The purpose of this blog is to report on my efforts to learn more about technology through the State Library's 21 things program.
Wednesday, March 18, 2015
RSS Readers
For the last year or so, I've been using NetVibes for my RSS Reader. I started using it when Google discontinued its "homepage" product. It was recommended in some article I read about replacements for the Google product.
I like that it is easy to add RSS feeds, and that you can easily change the interface from an integrated reader to its "application" page that allows you to view each feed in its own context. Here is what the integrated reader looks like:

I don't have a lot of feeds set up ... mostly because I am easily overwhelmed with too much data. I have been pretty happy with the Library Journal InfoDocket feed since it covers a wide range of library news.
I hope to add a few more blogs into the mix in the next year, since I'm going to be working harder at doing more professional reading around digital collections issues. Lots of folks blog on this topic, but some are really technical. I need to find good feed(s) that cover policy issues but also covers technical issues enough to keep me informed without making my eyes glaze over!
I like that it is easy to add RSS feeds, and that you can easily change the interface from an integrated reader to its "application" page that allows you to view each feed in its own context. Here is what the integrated reader looks like:
I don't have a lot of feeds set up ... mostly because I am easily overwhelmed with too much data. I have been pretty happy with the Library Journal InfoDocket feed since it covers a wide range of library news.
I hope to add a few more blogs into the mix in the next year, since I'm going to be working harder at doing more professional reading around digital collections issues. Lots of folks blog on this topic, but some are really technical. I need to find good feed(s) that cover policy issues but also covers technical issues enough to keep me informed without making my eyes glaze over!
Thursday, March 12, 2015
Google Drive
I have used Google Docs for several years to share documents among members of various committees I have been on. It worked really well for sharing documents when I was the chair of the Federal Depository Library Council, since we had members from all over the country. We also used it during our meetings to share notes and collaboratively draft recommendations.
Here at OSL, I've also used Google Drive for sharing documents. I used it to share the many files associated with the proposals we received for the recent RFP for the Statewide Database Licensing Program with committee members who were evaluating proposals. We have also been using a shared spreadsheet file to identify all the invited participants to the NW Digital Collections Summit meeting to be held here at OSL on March 20. Using Google Drive to share documents for short term work is much more efficient than setting up a web page. Also, the ability to "group edit" documents is extremely valuable.
Most recently, the Library Support and Development Division used a Google Document to work on our Division's strategic plan. We used a template document created by Katie to fill in information about how each of the programs/projects we work on fit into OSL's strategic imperatives. We went over instructions for filling out the template as a group, and then worked on it to individually fill out information about each of our projects/programs over the course of an afternoon. We then came together the following afternoon to review and edit the document.
We did struggle a bit with "version control", in that some of us that were not used to managing files in the Google Drive environment had trouble remembering not to "save" the document. When you use the save function in Google Docs, you create another version of the file that is no longer the same one that is being shared. You also have to remember that if you are the "owner" of the document, if you manipulate the file (rename, save a different version, etc.) that will impact the ability for others to access the document. Google Docs editing has some differences with Microsoft Word, so that can also be a bit challenging to get used to.
In all, I think Library Support's recent activity was a very good opportunity for everyone in the Division to either brush up or learn Google Drive skills ... exactly what we need to incorporate these tools into our daily work life.
Here at OSL, I've also used Google Drive for sharing documents. I used it to share the many files associated with the proposals we received for the recent RFP for the Statewide Database Licensing Program with committee members who were evaluating proposals. We have also been using a shared spreadsheet file to identify all the invited participants to the NW Digital Collections Summit meeting to be held here at OSL on March 20. Using Google Drive to share documents for short term work is much more efficient than setting up a web page. Also, the ability to "group edit" documents is extremely valuable.
Most recently, the Library Support and Development Division used a Google Document to work on our Division's strategic plan. We used a template document created by Katie to fill in information about how each of the programs/projects we work on fit into OSL's strategic imperatives. We went over instructions for filling out the template as a group, and then worked on it to individually fill out information about each of our projects/programs over the course of an afternoon. We then came together the following afternoon to review and edit the document.
We did struggle a bit with "version control", in that some of us that were not used to managing files in the Google Drive environment had trouble remembering not to "save" the document. When you use the save function in Google Docs, you create another version of the file that is no longer the same one that is being shared. You also have to remember that if you are the "owner" of the document, if you manipulate the file (rename, save a different version, etc.) that will impact the ability for others to access the document. Google Docs editing has some differences with Microsoft Word, so that can also be a bit challenging to get used to.
In all, I think Library Support's recent activity was a very good opportunity for everyone in the Division to either brush up or learn Google Drive skills ... exactly what we need to incorporate these tools into our daily work life.
Subscribe to:
Comments (Atom)