Tuesday, December 15, 2009
Monday, December 14, 2009
Reading Notes, Dec. 15
Cloud Computing:
There are different forms of cloud computing, f.e. utility computing (offering storage and virtual servers); offering web services (and not full applications); platforms to build your own service; MSP, such as remote virus scanning and anti-spam. The articel was particularly useful in conjunction with a recent article in OCLC Systems and Services on "Library in the Clouds," discussing the pros and cons of cloud computing for libraries.
The Future of the Library
The article argues that as more people are able to find information online, they are less likely to visit libraries, and libraries will have to re-define their roles. I found the article a bit over-general, and would have liked to see more discussion on the differences between different types of libraries. I also did not quite understand why the author thought libraries weren't culture-based in the past.
There are different forms of cloud computing, f.e. utility computing (offering storage and virtual servers); offering web services (and not full applications); platforms to build your own service; MSP, such as remote virus scanning and anti-spam. The articel was particularly useful in conjunction with a recent article in OCLC Systems and Services on "Library in the Clouds," discussing the pros and cons of cloud computing for libraries.
The Future of the Library
The article argues that as more people are able to find information online, they are less likely to visit libraries, and libraries will have to re-define their roles. I found the article a bit over-general, and would have liked to see more discussion on the differences between different types of libraries. I also did not quite understand why the author thought libraries weren't culture-based in the past.
Tuesday, December 8, 2009
Monday, November 30, 2009
Muddiest Point
Are there any non-commercial open source search engines that provide an alternative to google?
Reading Notes Dec. 1, 2009
Using a Wiki to Manage a Library Instruction Program
This article discusses a program to integrate wikis into library instruction at the library at East Tennessee State University, where the author is employed as reference librarian -- wikis are used to plan and expand on library instruction sessions -- professors can expand on specific questions they have during information sessions, or can help students to specify assignments for an instruction session.
Also, wikis can be used as a collaborative tool for exchanging information among instruction librarians. In addition, the article includes some helpful links to commercial sites with software allowing you to create your own wiki, as well as some background literature on wikis.
Creating the Academic Library Folksonomy
The article discusses how users can create folksonomy -- taxonomies of keywords created and shared by lots of users. Such folksonomies can help catalog useful internet sites, and integrate these folksonomies into academic libraries. This can provide quality indices of web sites, and also bring "grey" literature to light. The article gives a few examples of libraries that are trying out social tagging, f.e. the University of Pennsylvania, or Stanford University. Services uch as delicio or citeulike allow users to share these tags.
The article also discusses very briefly some of the risks and concerns about social tagging, for example spagging (spam tagging), or the variation of tags and the lack of controlled vocabulary. There are other concerns, not mentioned by the article, for example that tagging might provide institutions with a rationale to cut cataloging jobs, a discussion which has been held at the LC for a while, and an ongoing discussion whether or not it is useful to have controlled vocabularies to describe collections.
Weblogs: Their Use and Application in Science and Technology Libraries
Discusses the history of weblogs beginning in the early 1990s. Web logs are web sites that resemble personal journals, which allow visitors to comment on entries, and also include an archive of past weblogs. The authors highlight that web logs really took off in the late 1990s, when software package became available that allow users to build their own blogs. The article highlights web logs as a collaborative tool in science and technology libraries, which has some advatages over, for example email, since it is more easily searchable and can be organized according to specific subjects. RSS feeds can serve as a reminder to users to visit blogs. The article also explores reference blogs as an alternative to email. In blog instruction, librarians can have an important function, and train students in setting up and maintaining blogs. The article is from 2004 -- since then, many libraries have integrated blogs into their services..
Wikipedia
Interview with Jimmy Wales on Wikipedia -- the question here is to what extent the ideal of wikipedia matches the reality -- there was an article in Times Magazine, which Donna Guerin recommended for our LIS 2000 class, about some of the discrepancies: Wikipedia: A Victim of Its Own Success?
http://www.time.com/time/magazine/article/0,9171,1924492-1,00.html
These discrepancies suggest to take Jimmy Wales claims about wikipedia as this diverse, global, bottom-up project with a grain of salt, and rather reflect about persistent hierarchies in the way knowledge is created and organized.
This article discusses a program to integrate wikis into library instruction at the library at East Tennessee State University, where the author is employed as reference librarian -- wikis are used to plan and expand on library instruction sessions -- professors can expand on specific questions they have during information sessions, or can help students to specify assignments for an instruction session.
Also, wikis can be used as a collaborative tool for exchanging information among instruction librarians. In addition, the article includes some helpful links to commercial sites with software allowing you to create your own wiki, as well as some background literature on wikis.
Creating the Academic Library Folksonomy
The article discusses how users can create folksonomy -- taxonomies of keywords created and shared by lots of users. Such folksonomies can help catalog useful internet sites, and integrate these folksonomies into academic libraries. This can provide quality indices of web sites, and also bring "grey" literature to light. The article gives a few examples of libraries that are trying out social tagging, f.e. the University of Pennsylvania, or Stanford University. Services uch as delicio or citeulike allow users to share these tags.
The article also discusses very briefly some of the risks and concerns about social tagging, for example spagging (spam tagging), or the variation of tags and the lack of controlled vocabulary. There are other concerns, not mentioned by the article, for example that tagging might provide institutions with a rationale to cut cataloging jobs, a discussion which has been held at the LC for a while, and an ongoing discussion whether or not it is useful to have controlled vocabularies to describe collections.
Weblogs: Their Use and Application in Science and Technology Libraries
Discusses the history of weblogs beginning in the early 1990s. Web logs are web sites that resemble personal journals, which allow visitors to comment on entries, and also include an archive of past weblogs. The authors highlight that web logs really took off in the late 1990s, when software package became available that allow users to build their own blogs. The article highlights web logs as a collaborative tool in science and technology libraries, which has some advatages over, for example email, since it is more easily searchable and can be organized according to specific subjects. RSS feeds can serve as a reminder to users to visit blogs. The article also explores reference blogs as an alternative to email. In blog instruction, librarians can have an important function, and train students in setting up and maintaining blogs. The article is from 2004 -- since then, many libraries have integrated blogs into their services..
Wikipedia
Interview with Jimmy Wales on Wikipedia -- the question here is to what extent the ideal of wikipedia matches the reality -- there was an article in Times Magazine, which Donna Guerin recommended for our LIS 2000 class, about some of the discrepancies: Wikipedia: A Victim of Its Own Success?
http://www.time.com/time/magazine/article/0,9171,1924492-1,00.html
These discrepancies suggest to take Jimmy Wales claims about wikipedia as this diverse, global, bottom-up project with a grain of salt, and rather reflect about persistent hierarchies in the way knowledge is created and organized.
Monday, November 23, 2009
Monday, November 16, 2009
Sunday, November 15, 2009
Reading Notes November 17
Shreeves, S. L., Habing, T. O., Hagedorn, K., & Young, J. A. (2005). Current developments and future trends for the OAI protocol for metadata harvesting. Library Trends, 53(4), 576-589.
This text was not easy to understand, but here are some excerpts:
"The mission of the Open Archives Initiative (...) is to "develop and promote interoperability standards that aim to facilitate the efficient dissemination of content" (Open Archives Initiative, n.d. a). The Protocol for Metadata Harvesting, a tool developed through the OAI, facilitates interoperability between disparate and diverse collections of metadata through a relatively simple protocol based on common standards (XML, HTTP, and Dublin Core)."
"The OAI protocol requires that data providers expose metadata in at least unqualified Dublin Core; however, the use of other metadata schmas is possible and encouraged. The protocol can provide access to parts of the "invisible Web" that are not easily accessible to search engines
(such as resources within databases) (Sherman & Price, 2003) and can provide ways for communities of interest to aggregate resources from geographically diffuse collections."
-- The data is searchable and browsable without any manual cataloging of the various OAI repositories.
-- I could not pull up the text on how search engines work today, and will continue the reading tomorrow, once I get access to another computer.
White Paper: The Deep Web: Surfacing Hidden Value
Michael K. Bergman
Journal of Electronic Publishing, vol. 7, no. 1, August, 2001
DOI: http://dx.doi.org/10.3998/3336451.0007.104
-- This article is very enlightening -- it covers a technology (DeepPlanet, which can search the deep web)
-Most of the Web's information is buried far down on dynamically generated sites, and standard search engines never find it-- it si about 500 times the size of the surface web
--Traditional search engines create their indices by spidering or crawling surface Web pages. To be discovered, the page must be static and linked to other pages. Traditional search engines can not "see" or retrieve content in the deep Web
--The deep Web is qualitatively different from the surface Web. Deep Web sources store their content in searchable databases that only produce results dynamically in response to a direct request.
-- The deep web is a very coveted commodity
-- Study by NEC research initiative that search engine sby google and northern light only crawl 16% of the web's content
--Search engines obtain their listings in two ways: Authors may submit their own Web pages, or the search engines "crawl" or "spider" documents by following one hypertext link to another. The latter returns the bulk of the listings. Crawlers work by recording every hypertext link in every page they index crawling.
-- The crawls used to be indiscriminate, but "the most recent generation of search engines (notably Google) have replaced the random link-following approach with directed crawling and indexing based on the "popularity" of pages. In this approach, documents more frequently cross-referenced than other documents are given priority both for crawling and in the presentation of results. This approach provides superior results when simple queries are issued, but exacerbates the tendency to overlook documents with few links."
__ the problem here: without a linkage from another Web document, a page will never be discovered.
-- They don't use the term invisible web -- it is not invisible, but rather unindexable
-- the article continues to describe the study in more detail
--it is impossible to completely index the deep content, but new technologies need to be developed to search the complete web
Searching must evolve to encompass the complete Web.
This text was not easy to understand, but here are some excerpts:
"The mission of the Open Archives Initiative (...) is to "develop and promote interoperability standards that aim to facilitate the efficient dissemination of content" (Open Archives Initiative, n.d. a). The Protocol for Metadata Harvesting, a tool developed through the OAI, facilitates interoperability between disparate and diverse collections of metadata through a relatively simple protocol based on common standards (XML, HTTP, and Dublin Core)."
"The OAI protocol requires that data providers expose metadata in at least unqualified Dublin Core; however, the use of other metadata schmas is possible and encouraged. The protocol can provide access to parts of the "invisible Web" that are not easily accessible to search engines
(such as resources within databases) (Sherman & Price, 2003) and can provide ways for communities of interest to aggregate resources from geographically diffuse collections."
-- The data is searchable and browsable without any manual cataloging of the various OAI repositories.
-- I could not pull up the text on how search engines work today, and will continue the reading tomorrow, once I get access to another computer.
White Paper: The Deep Web: Surfacing Hidden Value
Michael K. Bergman
Journal of Electronic Publishing, vol. 7, no. 1, August, 2001
DOI: http://dx.doi.org/10.3998/3336451.0007.104
-- This article is very enlightening -- it covers a technology (DeepPlanet, which can search the deep web)
-Most of the Web's information is buried far down on dynamically generated sites, and standard search engines never find it-- it si about 500 times the size of the surface web
--Traditional search engines create their indices by spidering or crawling surface Web pages. To be discovered, the page must be static and linked to other pages. Traditional search engines can not "see" or retrieve content in the deep Web
--The deep Web is qualitatively different from the surface Web. Deep Web sources store their content in searchable databases that only produce results dynamically in response to a direct request.
-- The deep web is a very coveted commodity
-- Study by NEC research initiative that search engine sby google and northern light only crawl 16% of the web's content
--Search engines obtain their listings in two ways: Authors may submit their own Web pages, or the search engines "crawl" or "spider" documents by following one hypertext link to another. The latter returns the bulk of the listings. Crawlers work by recording every hypertext link in every page they index crawling.
-- The crawls used to be indiscriminate, but "the most recent generation of search engines (notably Google) have replaced the random link-following approach with directed crawling and indexing based on the "popularity" of pages. In this approach, documents more frequently cross-referenced than other documents are given priority both for crawling and in the presentation of results. This approach provides superior results when simple queries are issued, but exacerbates the tendency to overlook documents with few links."
__ the problem here: without a linkage from another Web document, a page will never be discovered.
-- They don't use the term invisible web -- it is not invisible, but rather unindexable
-- the article continues to describe the study in more detail
--it is impossible to completely index the deep content, but new technologies need to be developed to search the complete web
Searching must evolve to encompass the complete Web.
Muddiest Point November 10
I wasn't quite sure if The University of Pittsburgh had an institutional repository -- if it does, how can you access it?
Tuesday, November 3, 2009
Assignment 5: Koha
Here is the link to my Koha collection on managing oral history archives:
http://upitt04-staff.kwc.kohalibrary.com/cgi-bin/koha/virtualshelves/shelves.pl?viewshelf=39
http://upitt04-staff.kwc.kohalibrary.com/cgi-bin/koha/virtualshelves/shelves.pl?viewshelf=39
Monday, November 2, 2009
Muddiest Point, Week 10
I don't have a muddiest point for last week, but I do have several for this week. Here is one:
The article by Bergholz on xml was very helpful. It was, however, somewhat dated (from 2000). What has happened since the article was published -- have xml schemas replaced dtds? How have the development of rdfs and doms advanced since 2000?
The article by Bergholz on xml was very helpful. It was, however, somewhat dated (from 2000). What has happened since the article was published -- have xml schemas replaced dtds? How have the development of rdfs and doms advanced since 2000?
Reading Notes Week 10 (November 10)
Bergholz, XML Tutorial
The article by Andre Bergholz is the clearest of all assigned articles, and I understood the other articles better after reading it. I really liked that he included examples, and also used library catalog examples, so you can see how it is applied in the library environment. It is, however, somewhat dated (from 2000), so it would be nice to read an up-to-date version of this on xml.
-- makes clear that html is layout oriented, whereas xml is structure oriented
-- both sgml and html influenced the development of xml
-- xml is about meaningful annotation
-- syntactically, xml looks like html
-- well formed document begins with prologue and has one element, and additional number of instructions can be added
-- dtds define the structure of xml documents
-- dtd elements can be nonterminal or terminal
-- elements can have zero or more attributes
-- extensions to xml include namespaces and addressing and linking capabilities
-- namespaces and dtds do not work well together
-- in html, links only point to a document
-- html is one-way
- xml extends htmls linking capacities
-- extended links connect more than one document
-- there is also an extensible stylesheet language, two languages: a transformation language and a formatting language
-- dtds have disadvantages and xml schemas address these disadvantages
-- xml schemas is well formed xml
-- the goal is to replace dtds
-- development of rdfs and doms also affect xml
Ogbuji, A Survey of XML Standards
--The world of XML is growing, with a huge variety of standards and technologies that interact in complex ways.
-- Points out that it can be difficult for beginners to navigate the most important aspects of XML, and for users to keep track of new entries and changes in the space
--includes a list of resources, if we want to explore this in more detail
XML Schema Tutorial
--XML Schemas are successors of DDT (document type definition)
--XML Schemas secure data communications
--they are extensible
--the schema element is rot of every schema
--xml schemas define elemnst of xml files
--attributes are complex
--restrictions on attributes are facets
--a complex element contains other elements or attributes
Martin Bryan. Introducing the Extensible Markup Language (XML)
This article was very difficult to follow for a non-programmer. What I understood from it, however, was that xml defines the structure of a document, rather than its appearance (like html). Therefore, xml is ideal for databases, so it can pull different elements from different locations together. “By storing data in the clearly defined format provided by XML you can ensure that your data will be transferable to a wide range of hardware and software environments. New techniques in programming and processing data will not affect the logical structure of your document's message.”
The article by Andre Bergholz is the clearest of all assigned articles, and I understood the other articles better after reading it. I really liked that he included examples, and also used library catalog examples, so you can see how it is applied in the library environment. It is, however, somewhat dated (from 2000), so it would be nice to read an up-to-date version of this on xml.
-- makes clear that html is layout oriented, whereas xml is structure oriented
-- both sgml and html influenced the development of xml
-- xml is about meaningful annotation
-- syntactically, xml looks like html
-- well formed document begins with prologue and has one element, and additional number of instructions can be added
-- dtds define the structure of xml documents
-- dtd elements can be nonterminal or terminal
-- elements can have zero or more attributes
-- extensions to xml include namespaces and addressing and linking capabilities
-- namespaces and dtds do not work well together
-- in html, links only point to a document
-- html is one-way
- xml extends htmls linking capacities
-- extended links connect more than one document
-- there is also an extensible stylesheet language, two languages: a transformation language and a formatting language
-- dtds have disadvantages and xml schemas address these disadvantages
-- xml schemas is well formed xml
-- the goal is to replace dtds
-- development of rdfs and doms also affect xml
Ogbuji, A Survey of XML Standards
--The world of XML is growing, with a huge variety of standards and technologies that interact in complex ways.
-- Points out that it can be difficult for beginners to navigate the most important aspects of XML, and for users to keep track of new entries and changes in the space
--includes a list of resources, if we want to explore this in more detail
XML Schema Tutorial
--XML Schemas are successors of DDT (document type definition)
--XML Schemas secure data communications
--they are extensible
--the schema element is rot of every schema
--xml schemas define elemnst of xml files
--attributes are complex
--restrictions on attributes are facets
--a complex element contains other elements or attributes
Martin Bryan. Introducing the Extensible Markup Language (XML)
This article was very difficult to follow for a non-programmer. What I understood from it, however, was that xml defines the structure of a document, rather than its appearance (like html). Therefore, xml is ideal for databases, so it can pull different elements from different locations together. “By storing data in the clearly defined format provided by XML you can ensure that your data will be transferable to a wide range of hardware and software environments. New techniques in programming and processing data will not affect the logical structure of your document's message.”
Sunday, October 25, 2009
Reading Notes Week 9 (Oct. 27)
Goans, D., Leach, G., & Vogel, T. M. (2006). Beyond HTML: Developing and re-imagining library web guides in a content management system.
This article addresses and evaluates a common problem at many libraries -- a multiplicity of static html content guides put together by different liaison librarians. By developing a CMS, the library at GSU was able to separate content, which was collected in a MYSQL database, from layout and design, and create a more coherent, dynamic system. The system continued to give librarians flexibility when working with their content guides. the article also highlighted that training of both users and librarians is instrumental when implementing a CMS.
HTML Cheatsheet - this is a very straightforward site that gives you an overview of html code that allows you to fix the code in your web pages -- working directly with html gives you sometimes more control over your site than working with design software like dreamweaver alone.
W3 School Cascading Style Sheet Tutorial: helpful for a quick introduction to CSS.
This article addresses and evaluates a common problem at many libraries -- a multiplicity of static html content guides put together by different liaison librarians. By developing a CMS, the library at GSU was able to separate content, which was collected in a MYSQL database, from layout and design, and create a more coherent, dynamic system. The system continued to give librarians flexibility when working with their content guides. the article also highlighted that training of both users and librarians is instrumental when implementing a CMS.
HTML Cheatsheet - this is a very straightforward site that gives you an overview of html code that allows you to fix the code in your web pages -- working directly with html gives you sometimes more control over your site than working with design software like dreamweaver alone.
W3 School Cascading Style Sheet Tutorial: helpful for a quick introduction to CSS.
Muddiest Point Week 8/9
How do the ranking systems of different search engines -- f. e. yahoo or chrome -- differ from google's algorithm system?
Sunday, October 18, 2009
Muddiest Point (Readings Oct. 20)
Where does Google find the information for its indices of web sites-- on the individual servers?
Reading Notes, Week 7/8 (Oct. 20)
Brin and Page on Google
I don’t like much of Google’s pompous rhetoric in general; and you can’t expect the founders of Google to be more modest or critical about their company, but other than saying that Google is great, they didn’t really say much of any substance about the way the search engine works. In terms of understanding the inner life of Google, the text by Brin and Page, on the “Anatomy of a Large-Scale Hypertextual Web Search Engine,” (text from Lis 2000) was more enlightening. Still, there is the fundamental problem of the lack of transparency about Google’s algorithm and the way pages are being ranked, which contradicts this rhetoric of openness and all-inclusiveness, which also glosses over the fact that, while Google may index millions of sites, a lot of other sites are missed by the way the pages are being ranked. Google “will never exhaust the store and meaning of the Web,” wrote Terrence Brooks in his text we read in Lis 2000, “The nature and meaning in the age of Google.” (Information Research, vol. 9. no. 3 (April 2004) I was somewhat puzzled about their statement that Google is pretty much everywhere where there is power, leaving out a critical piece of the chain, the phone and cable companies, the internet service providers, on which almost all access – and lack of access-- depends. So, aggregated on a screen at Google headquarters in Mountain View it may look as if Google is everywhere, but of course this is not true, certainly not in the US, and not in Europe, where a lot of people just do not have and can’t afford internet access through expensive providers. And the way they talked about lack of Google use in Africa, it just sounded as if it were one big market that can and should be conquered – not much of reflection about the many digital divides here as well.
How Internet Infrastructure Works
--Network hierarchy, connected trough POP’s, and NAP’s
-- the internet as a collection of huge corporate networks that all communicate with each other at NAP’s
-- they rely on backbones (fiber optic trunk lines) and routers to talk to each other
-- who pays for the backbones?
-- you can identify net and host through IP address
-- DNS (domain name servers) convert domain names into IP addresses
Andrew Pace, Dismantling Integrated Library Systems, Library Journal, 2/1, 2004
-Web is fueling changes in the ILS
--Problems with the inter-operability of ILS "Today, interoperability in library automation is more myth than reality. Some of us wonder if we may lose more than we gain in this newly dismantled world."
-- There are many vendors, many systems, in many libraries, only pieces operate together
-There are some attempts to start from scratch
-- Better systems costs more -- libraries save at the wrong spot
--Some of the best ideas have come from librarians
--open source is a possibility, but not fully developed(as of 2004)
-- the future lies in integration and re-integration
-- has this chnaged?
I don’t like much of Google’s pompous rhetoric in general; and you can’t expect the founders of Google to be more modest or critical about their company, but other than saying that Google is great, they didn’t really say much of any substance about the way the search engine works. In terms of understanding the inner life of Google, the text by Brin and Page, on the “Anatomy of a Large-Scale Hypertextual Web Search Engine,” (text from Lis 2000) was more enlightening. Still, there is the fundamental problem of the lack of transparency about Google’s algorithm and the way pages are being ranked, which contradicts this rhetoric of openness and all-inclusiveness, which also glosses over the fact that, while Google may index millions of sites, a lot of other sites are missed by the way the pages are being ranked. Google “will never exhaust the store and meaning of the Web,” wrote Terrence Brooks in his text we read in Lis 2000, “The nature and meaning in the age of Google.” (Information Research, vol. 9. no. 3 (April 2004) I was somewhat puzzled about their statement that Google is pretty much everywhere where there is power, leaving out a critical piece of the chain, the phone and cable companies, the internet service providers, on which almost all access – and lack of access-- depends. So, aggregated on a screen at Google headquarters in Mountain View it may look as if Google is everywhere, but of course this is not true, certainly not in the US, and not in Europe, where a lot of people just do not have and can’t afford internet access through expensive providers. And the way they talked about lack of Google use in Africa, it just sounded as if it were one big market that can and should be conquered – not much of reflection about the many digital divides here as well.
How Internet Infrastructure Works
--Network hierarchy, connected trough POP’s, and NAP’s
-- the internet as a collection of huge corporate networks that all communicate with each other at NAP’s
-- they rely on backbones (fiber optic trunk lines) and routers to talk to each other
-- who pays for the backbones?
-- you can identify net and host through IP address
-- DNS (domain name servers) convert domain names into IP addresses
Andrew Pace, Dismantling Integrated Library Systems, Library Journal, 2/1, 2004
-Web is fueling changes in the ILS
--Problems with the inter-operability of ILS "Today, interoperability in library automation is more myth than reality. Some of us wonder if we may lose more than we gain in this newly dismantled world."
-- There are many vendors, many systems, in many libraries, only pieces operate together
-There are some attempts to start from scratch
-- Better systems costs more -- libraries save at the wrong spot
--Some of the best ideas have come from librarians
--open source is a possibility, but not fully developed(as of 2004)
-- the future lies in integration and re-integration
-- has this chnaged?
Comments Week 7 or 8 (Oct. 20)
Commented on:
http://preservingtim.blogspot.com/
And on:
http://jonwebsterslis2600blog.blogspot.com
http://preservingtim.blogspot.com/
And on:
http://jonwebsterslis2600blog.blogspot.com
Saturday, October 10, 2009
Assignment 4: Working with Jing
Exploring the World Digital Library
1. http://www.flickr.com/photos/42354457@N07/3998337729/?addedcomment=1#comment72157622557339392
2. http://www.flickr.com/photos/42354457@N07/3999108966/sizes/o/
3. http://www.flickr.com/photos/42354457@N07/3999121772/
4. http://www.flickr.com/photos/42354457@N07/3999129796/
5. http://www.flickr.com/photos/42354457@N07/3998371253/
6. http://www.flickr.com/photos/42354457@N07/3999149030/
7. http://www.flickr.com/photos/42354457@N07/3999207116/
Link to my thriller on the World Digital Library:
http://www.screencast.com/users/Khering145/folders/Jing/media/867a7e7d-2926-49ac-8306-a3a4f0b128fe
1. http://www.flickr.com/photos/42354457@N07/3998337729/?addedcomment=1#comment72157622557339392
2. http://www.flickr.com/photos/42354457@N07/3999108966/sizes/o/
3. http://www.flickr.com/photos/42354457@N07/3999121772/
4. http://www.flickr.com/photos/42354457@N07/3999129796/
5. http://www.flickr.com/photos/42354457@N07/3998371253/
6. http://www.flickr.com/photos/42354457@N07/3999149030/
7. http://www.flickr.com/photos/42354457@N07/3999207116/
Link to my thriller on the World Digital Library:
http://www.screencast.com/users/Khering145/folders/Jing/media/867a7e7d-2926-49ac-8306-a3a4f0b128fe
Subscribe to:
Posts (Atom)
