Skip to main content

Home/ IMT122 OUA Group/ Group items tagged community

Rss Feed Group items tagged

Joanne S

What is social software? In Social software in libraries: building collaboration, commu... - 0 views

  •  
    Farkas, M. G. (2007). What is social software? In Social software in libraries: building collaboration, communication, and community online. Information Today, Inc. Retrieved from http://www.sociallibraries.com/farkaschap1.pdf
Joanne S

Mobile Strategy | National Library of Australia - 0 views

  • must move towards a model with comprehensive mobile access to online services
  • mobile’ has come to encompass an ever-expanding field of devices, platforms and content
  • Smart (internet enabled) or dumb/cellular
  • ...98 more annotations...
  • Supplied (on-site device distribution) or privately owned
  • Native apps
  • Mobile websites
  • In terms of content this includes:
  • Applications (software designed for specific tasks
  • Podcasts (audio and video content
  • Other downloadable content (e.g. PDFs and ebook
  • the Library may look to harness the potential of these technologies to break away from the traditional broadcast-only website presence and move towards two-way conversations between the Library and its users, or conversations between the users themselves
  • the key objectives stated in the Information Technology Strategic Plan 2012-2015 include Online Presence and supporting “the needs of our users for easy discovery of, access to, and engagement with our services, collections and other information resources in the digital environment”
  • ensure equal access to our resources and services for all Australians.
  • facilitate equal access to Library resources for everyone.
  • Putting Library resources into the hands of users in their lounge rooms reflects a deeper understanding of the need to move beyond the desire to follow our users and instead reach out to them to “take them some place new
  • mobile will only continue to grow and overtake desktop internet usage within 2-3 years
  • building both infrastructure and a culture of engagement will pave the way to more efficiently and effectively meeting that need in the future
  • 4         Strategic goals
  • Improve access to our collection and services for audiences, wherever they are, whether on-site or anywhere else in the world.
  • Equip staff to champion and drive the development of mobile services to improve access and productivity.
  • Adopt an evidence-based approach to service development and delivery
  • Modernise the Library brand to reflect relevance, accessibility and innovation.
  • Create opportunities for learning
  • Facilitate connections, conversation and overall engagement with national collection material.
  • Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
  • Build, consolidate and share expertise
  • Adopt standards and best practices for interoperable mobile content and cross-platform data management.
  • A focus on strategic, audience-driven activity with a utility function.
  • Seek out and engage new technologies to achieve marketing and communications goals.
  • 6         Recommended activities
  • activities provide a means to implement and ground the strategy with specific and measurable tasks
  • 6.1      Governance and infrastructure
  • The Library’s IT Strategy Group will determine priorities
  • formalising the Web Committee’s role as an advisory body
  • Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
  • Information Technology Division to examine ongoing resourcing of development work, administrative models, and potential for partial cost-recovery
  • Adopt emerging Commonwealth requirements and advice pertaining to managing devices and content
  • Develop and review policy in support of the use of both enterprise devices and use of personal devices for work-related purposes. Identify
  • Investigate infrastructure and resourcing requirements for digital recording and distribution
  • Collections Management Division to keep a watching brief on any developments pertaining to the extension of Legal Deposit to include digital (and mobile) content
  • developing a statement of collecting intentions for the various categories of ebook titles within the context of revising the collecting policy for Australian electronic publications in general
  • Applications
  • Podcasts (audio and video content
  • Other downloadable content (e.g. PDFs and ebooks
  • 3         Our mobile vision
  • Improve access to our collection and services for audiences, wherever they are, whether on-site or anywhere else in the world.
  • 4         Strategic goals
  • 3         Our mobile vision
  • 4         Strategic goals
  • 3         Our mobile vision
  • Improve access to our collection and services for audiences, wherever they are, whether on-site or anywhere else in the world.
  • 4         Strategic goals
  • Adopt an evidence-based approach to service development and delivery
  • Equip staff to champion and drive the development of mobile services to improve access and productivity.
  • Modernise the Library brand to reflect relevance, accessibility and innovation.
  • Adopt an evidence-based approach to service development and delivery
  • Equip staff to champion and drive the development of mobile services to improve access and productivity.
  • Create opportunities for learning
  • Facilitate connections, conversation and overall engagement with national collection material.
  • Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
  • Tactics
  • Equip staff to champion and drive the development of mobile services to improve access and productivity.
  • Adopt an evidence-based approach to service development and delivery
  • Modernise the Library brand to reflect relevance, accessibility and innovation.
  • Create opportunities for learning
  • Facilitate connections, conversation and overall engagement with national collection material.
  • Tactics
  • Tactics
  • Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
  • Build, consolidate and share expertise
  • Tactics
  • Establish and expand the infrastructure and back-end systems required to support mobile initiatives, products and services.
  • Build, consolidate and share expertise
  • Adopt standards and best practices for interoperable mobile content and cross-platform data management.
  • Build, consolidate and share expertise
  • Adopt standards and best practices for interoperable mobile content and cross-platform data management.
  • A focus on strategic, audience-driven activity with a utility function.
  • Adopt standards and best practices for interoperable mobile content and cross-platform data management.
  • A focus on strategic, audience-driven activity with a utility function.
  • Seek out and engage new technologies to achieve marketing and communications goals.
  • Seek out and engage new technologies to achieve marketing and communications goals.
  • Recommended
  • 6.1      Governance and infrastructure
  • Library’s IT Strategy Group will determine priorities
  • formalising the Web Committee
  • Information Technology Division to examine ongoing resourcing
  • formalising the Web Committee
  • Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
  • Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
  • formalising the Web Committee
  • Develop and review policy in support of the use of both enterprise devices and use of personal devices for work-related purposes
  • Investigate infrastructure and resourcing requirements for digital recording and distribution to ensure the long-term sustainability of online broadcast activity
  • Adopt emerging Commonwealth requirements and advice pertaining to managing devices and content
  • formalising the Web Committee
  • Information Technology Division to examine ongoing resourcing
  • Include requisite support for mobile content collection, preservation and access in the Digital Library Infrastructure Replacement Project (DLIR
  • Adopt emerging Commonwealth requirements and advice pertaining to managing devices and content
  • Collections Management Division to keep a watching brief on any developments pertaining to the extension of Legal Deposit to include digital (and mobile) conten
  • developing a statement of collecting intentions for the various categories of ebook titles within the context of revising the collecting policy for Australian electronic publications
  • Adopt emerging Commonwealth requirements and advice pertaining to managing devices and content
  • Develop and review policy in support of the use of both enterprise devices and use of personal devices for work-related purposes
Joanne S

A social media policy for a one branch public library » Librarians Matter - 1 views

  • “Social Media.” includes community created content sites like Blogs, Forums, Flickr, YouTube, Wikis, Social Networks, Twitter and other content sharing sites.
  • When you use social media your behaviour  and content is not only a reflection of you but also of (our) Library.
  • Social Media Do’s Be Professional – Talk the way you would talk to real people in professional situations. Be Courteous – Be sure to listen & ask questions. Be Accurate – Check your facts before you post and provide supporting sources if necessary. Be Useful – Add content because you have something interesting to say, not for the sake of regular posting. Be Intelligent – Provide some value. Don’t talk down. Offer insight. Be Conversational –  Avoid overly pedantic or “composed” language. Don’t be afraid to bring in your own personality. Be Non-confrontational – If you disagree, do so respectfully Be Prompt – If you need to moderate or respond to a comment do so as quickly as possible Be Identifiable – Use your real name and do not post anonymously. Be Transparent – Disclose that you work for the library if this is relevant and be honest & truthful. Social Media Don’ts Don’t Share Secrets –If you aren’t sure you can disclose something, just don’t do it. Think about privacy, confidentiality and permission to use other people’s content. Don’t Bad Mouth – Keep the language clean & avoid slamming people or companies. Don’t Complain – If you don’t have anything nice to say, don’t say anything at all. Don’t do Stupid Things – If it doesn’t help the Library or our community, don’t do it. Don’t Defame – Show everyone respect. Don’t Forget your day job –Social Media can consume you so don’t forget your other duties. Moderate, balanced use is essential.
  •  
    Greenhill, K., & Fay, J. (2010, September 10). A social media policy for a one branch public library. Librarians Matter. Retrieved October 1, 2010, from http://librariansmatter.com/blog/2010/09/10/a-social-media-policy-for-a-one-branch-public-library/
Joanne S

VALA2012 Session 12 Warren - VALA - 0 views

  •  
    NATIONAL AND STATE LIBRARIES OF AUSTRALASIA'S LIBRARY HACK PROJECT Warren, M., & Hayward, R. (2012). Hacking the nation: Libraryhack and community-created aps. VALA 2012: eM-powering eFutures. Presented at the VALA 2012: eM-powering eFutures, Melbourne Australia: VALA: Libraries, technology and the future. Retrieved from http://www.vala.org.au/vala2012-proceedings/vala2012-session-12-warren
Michelle Pitman

NCDD Community News » What We're All About - 0 views

  •  
    This has me wondering if this is a part of the future of libraries!  What a fantastic innovation!  So positive and positively people-focussed.  Finding solutions to tough issues through dialogue and practical conversations.  There are important resources here!  
Joanne S

W3C Library Linked Data Incubator Group - 0 views

  • mission of the Library Linked Data incubator group is to help increase global interoperability of library data on the Web, by bringing together people involved in Semantic Web activities—focusing on Linked Data—in the library community and beyond, building on existing initiatives, and identifying collaboration tracks for the future.
  • existing building blocks of librarianship, such as metadata models, metadata schemas, standards and protocols for building interoperability and library systems and networked environments, encourage libraries to bring their content, and generally re-orient their approaches to data interoperability towards the Web, also reaching to other communities.
  •  
    W3C Library Linked Data Incubator Group. (n.d.).  Retrieved  from http://www.w3.org/2005/Incubator/lld/ .  Browse the documents associated with this site from a group that formed mid-2010 to look at how library data can be exposed as Linked Data.
Joanne S

Egypt enters communication blackout with disruption to internet, SMS, and BlackBerry me... - 0 views

  • hard data showing that almost all routes for exchanging internet traffic with the country have been shut down
  • clearly an extreme step for any government to take
  •  
    "In Egypt in early 2011, during the revolution the government cut off the internet between 27 January and 2 February. These links were shared by Farah, a previous student who was in Egypt during this period."
Joanne S

The Code4Lib Journal - How Hard Can It Be? : Developing in Open Source - 0 views

  • We experienced freedom to explore alternate avenues, to innovate, to take risks in ways that would have been difficult under the direct control of a district council.
  • patrons made it clear that while they appreciated that computers were a necessary part of a modern library, they did not consider them the most important part.
  • Our overall objective was to source a library system which: could be installed before Y2K complications immobilised us, was economical, in terms of both initial purchase and future license and maintenance support fees, ran effectively and fast by dial-up modem on an ordinary telephone line, used up-to-the minute technologies, looked good, and was easy for both staff and public to use, took advantage of new technology to permit members to access our catalogue and their own records from home, and let us link easily to other sources of information – other databases and the Internet. If we could achieve all of these objectives, we’d be well on the way to an excellent service.
  • ...14 more annotations...
  • "How hard can it be" Katipo staff wondered, "to write a library system that uses Internet technology?" Well, not very, as it turned out.
  • Koha would thus be available to anyone who wanted to try it and had the technical expertise to implement it.
  • fairly confident that we already had a high level of IT competence right through the staff, a high level of understanding of what our current system did and did not do.
  • ensure the software writers did not miss any key points in their fundamental understanding of the way libraries work.
  • The programming we commissioned cost us about 40% of the purchase price of an average turn-key solution.
  • no requirement to purchase a maintenance contract, and no annual licence fees.
  • An open source project is never finished.
  • Open source projects only survive if a community builds up around the product to ensure its continual improvement. Koha is stronger than ever now, supported by active developers (programmers) and users (librarians)
  • There are a range of support options available for Koha, both free and paid, and this has contributed to the overall strength of the Koha project.
  • Vendors like Anant, Biblibre, ByWater, Calyx, Catalyst, inLibro, IndServe, Katipo, KohaAloha, LibLime, LibSoul, NCHC, OSSLabs, PakLAG, PTFS, Sabinet, Strategic Data, Tamil and Turo Technology take the code and sell support around the product, develop add-ons and enhancements for their clients and then contribute these back to the project under the terms of the GPL license.
  • FRBR [5] arrangement, although of course it wasn’t called that 10 years ago, it was just a logical way for us to arrange the catalogue. A single bibliographic record essentially described the intellectual content, then a bunch of group records were attached, each one representing a specific imprint or publication.
  • The release of Koha 3.0 in late 2008 brought Koha completely into the web 2.0 age and all that entails. We are reconciled to taking a small step back for now, but the FRBR logic is around and RDA should see us back where want to be in a year or so – but with all the very exciting features and opportunities that Koha 3 has now.
  • In the early days, the Koha list appeared to have been dominated by programmers but I have noticed a lot more librarians participating now
  • "Adopt technology that keeps data open and free, abandon[ing] technology that does not." The time is right for OSS.
  •  
    For more information about Koha and how it was developed, see: Ransom, J., Cormack, C., & Blake, R. (2009). How Hard Can It Be? : Developing in Open Source. Code4Lib Journal, (7). Retrieved from http://journal.code4lib.org/articles/1638
Joanne S

Metadata schema in the cultural heritage sector - 1 views

  • The sheer number of metadata standards in the cultural heritage sector is overwhelming, and their inter-relationships further complicate the situation. This visual map of the metadata landscape is intended to assist planners with the selection and implementation of metadata standards.
  • 05 standards listed here is evaluated on its strength of application to defined categories in each of four axes: community, domain, function, and purpose.
  •  
    Metadata schema in the cultural heritage sector Riley, J. (2010). Seeing Standards: a visualisation of the metadata universe. Retrieved January 13, 2011, from http://www.dlib.indiana.edu/~jenlrile/metadatamap/
Joanne S

Reprogramming The Museum | museumsandtheweb.com - 0 views

  • Powerhouse experie
  • her APIs
  • Flickr AP
  • ...23 more annotations...
  • Thomson Reuters OpenCalais
  • OCLC's WorldCat
  • Before we began our work on the Commons on Flickr, some museum colleagues were concerned that engaging with the Flickr community would increase workloads greatly. While the monitoring of the site does take some work, the value gained via the users has far outweighed any extra effort. In some cases, users have dated images for us.
  • In subsequent use of the Flickr API, we appropriated tags users had added to our images, and now include them in our own collection database website (OPAC). We also retrieved geo-location data added to our images for use in third party apps like Sepiatown and Layar.
  • In our case the purpose of creating an API was to allow others to use our content.
  • So consider the questions above not in the context of should we or shouldn't we put our data online (via an API or otherwise) but rather in the context of managing expectations of the data's uptake.
  • Steps to an API
  • several important things which had to happen before we could provide a public web API. The first was the need to determine the licence status of our content.
  • The drive to open up the licensing of our content came when, on a tour we conducted of the Museum's collection storage facilities for some Wikipedian
  • This prompted Seb Chan to make the changes required to make our online collection documentation available under a mix of Creative Commons licences. (Chan, April 2009)
  • Opening up the licensing had another benefit: it meant that we had already cleared one hurdle in the path to creating an API.
  • The Government 2.0 Taskforce (http://gov2.net.au/about/) was the driver leading us to take the next step.
  • "increasing the openness of government through making public sector information more widely available to promote transparency, innovation and value adding to government information"
  • the first cultural institution in Australia to provided a bulk data dump of any sort.
  • The great thing about this use is that it exposes the Museum and its collection to the academic sector, enlightening them regarding potential career options in the cultural sector.
  • I will briefly mention some of the technical aspects of the API now for those interested. In line with industry best practice the Powerhouse Museum is moving more and more to open-source based hosting and so we chose a Linux platform for serving the API
  • Images are served from the cloud as we had already moved them there for our OPAC, to reduce outgoing bandwidth from the Museum's network.
  • Once we had the API up and running, we realised it would not be too much work to make a WordPress plug-in which allowed bloggers to add objects from our collection to their blogs or blog posts. Once built, this was tested internally on our own blogs. Then in early 2011 we added it to the WordPress plugin directory: http://wordpress.org/extend/plugins/powerhouse-museum-collection-image-grid/
  • One of the main advantages the API has over the data dump is the ability to track use.
  • It is also worth noting that since the API requests usually do not generate pages that are rendered in a browser it is not possible to embed Google Analytics tracking scripts in the API's output.
  • y requiring people to sign up using a valid email address before requesting an API key we are able to track API use back to individuals or organisations.
  • Concerns that people would use the API inappropriately were dealt with by adding a limit to the number of requests per hour each key can generate
  • An Application Programming Interface (API) is a particular set of rules and specifications that a software program can follow to access and make use of the services and resources provided by another particular software program
  •  
    Dearnley, L. (2011). Repreogramming the museum. In Museums and the Web 2011 : Proceedings. Presented at the Museums and the Web 2011, Toronto: Archives & Museum Informatics. Retrieved from http://conference.archimuse.com/mw2011/papers/reprogramming_the_museum
Joanne S

What is Cloud Computing and How will it Affect Libraries? | TechSoup for Libraries - 0 views

  • If you’ve used any of the popular Web 2.0 services over the past few years (e.g. Gmail, Wikipedia, Flickr or Twitter), you already have some experience with cloud computing
  • Like water and electricity, a computing cloud is a communally-shared resource that you lease on a metered basis, paying for as little or as much as you need, when you need it
    • Joanne S
       
      Benefits-  Cost Savings, Flexibility and Innovation.
  • ...4 more annotations...
  • As individuals and members of organizations, we’re already choosing between desktop applications and cloud applications when it comes to e-mail, RSS, file storage, word processing and other simple applications. Sooner or later we’ll have to make this choice for mission-critical enterprise applications too
  • Libraries may soon be building and managing their own data centers.
  • For more practical, technical explanations of cloud computing, check out the Wikipedia article the Anatomy of Cloud Computing the MIT Technology Review Briefing on Cloud Computing.
  • For a discussion of problems and concerns about the digital cloud, read: How Secure is Cloud Computing? Security in the Ether Industry Challenges: The Standards Question
Joanne S

Scot Colford, "Explaining free and Open Source software," - 0 views

  • Ten criteria must be met in order for a software distribution to be considered open source:
  • Free redistribution
  • the source code freely available to developers.
  • ...13 more annotations...
  • The license must permit modifications
  • Integrity of the author's source code
  • No discrimination against persons or groups
  • No discrimination against fields of endeavor
  • same license must be passed on to others when the program is redistributed.
  • License must not be specific to a product
  • License must not restrict other software
  • License must be technology-neutral
  • list of the nine most widely used licenses is
  • Apache Software License 2.0 (www.apache.org/licenses/LICENSE-2.0.html) New BSD License (www.opensource.org/licenses/bsd-license.php) GNU General Public License (GPL) (www.gnu.org/licenses/gpl.html) GNU Lesser General Public License (LGPL) (www.gnu.org/licenses/lgpl.html) MIT License (www.opensource.org/licenses/mit-license.php) Mozilla Public License 1.1 (MPL) (www.mozilla.org/MPL/MPL-1.1.html) Common Development and Distribution License (www.sun.com/cddl/cddl.html) Common Public License 1.0 (www.ibm.com/developerworks/library/os-cpl.html)  Eclipse Public License (www.eclipse.org/legal/epl-v10.html) [5].
  • common misconception, alluded to above, is that since the source code is freely distributed without royalty or licensing fee, open source applications are free of cost.
  • Free and open source software application users, on the other hand, must rely on development communities for support.
  • The pervasiveness of the World Wide Web guarantees that nearly every information organization is using free or open source software to perform some function.
Joanne S

K. G Schneider, "The Thick of the Fray: Open Source Software in Libraries in the First ... - 0 views

  • the vast majority of libraries continue to rely on legacy proprietary systems
  • libraries using open source integrated library systems indicates that the vast majority of libraries continue to rely on legacy proprietary systems
  • there are at least a dozen active OSS projects based in or with their genesis in library organizations
  • ...10 more annotations...
  • xCatalog
  • LibraryFind
  • Blackligh
  • iVia,
  • What makes OSS different from proprietary software is that it is free in every sense of the word: free as in “no cost,” free as in “unencumbered” and free as in “not locked up.”
  • questioned whether OSS is overall less expensive than its proprietary counterparts and has called for libraries to look hard at cost factors
  • OSS projects are thriving communities with leaders, followers, contributors, audiences and reputation systems.
  • Like so many things librarians hold dear – information, books and library buildings themselves – OSS is open, available and visible for all to see
  • OSS presents important opportunities for libraries
  • This is the world we want to be in again. It will not always be easy, and there will be a few spectacular failures. But there will also be spectacular successes – and this time, they will happen in the open.
Michelle Pitman

Democrasoft - Social Collaboration & Voting Platforms for Building Online Communities - 0 views

  •  
    Astonishing developments in online collaborative tools may not replace the real life "Town Hall" meetings, but they will further democratise difficult discussions.  Fantastic stuff!   
Joanne S

safer internet group - 5 Point Plan - 0 views

  • The Safer Internet Group brings together a diverse group of stakeholders who all share the goal of developing the Internet as a platform for education, communication and economic activity.
  • Australia needs to take effective action to ensure that Internet users, and particularly children, have a safe experience online, while ensuring that the benefits of the open Internet are available to all Australians.
  • We believe our way is comprehensive and practical. More importantly, we know it works. It delivers:
  • ...5 more annotations...
  • . More Effective Education
  • Comprehensive Policing of Illegal material on the Internet
  • User Tools that work
  • A new dialogue about Internet safety
  • Targeted Research of Internet Risks and Opportunities for Young People
  •  
    Safer Internet Group (2009) 5 Point Plan. Retrieved from http://www.saferinternetgroup.org/5pointplan.html (The Australian Library and Information Association is one of the members of the Safer Internet Group)
Joanne S

Companies and information: The leaky corporation | The Economist - 0 views

  • the WikiLeaks threat and the persistent leaking of other supposedly confidential corporate information have brought an important issue to the fore.
  • Companies are creating an ever-growing pile of digital information, from product designs to employees' e-mails.
  • Much of this information would do little damage if it seeped into the outside world; some of it, indeed, might well do some good. But some could also be valuable to competitors—or simply embarrassing—and needs to be protected. Companies therefore have to decide what they should try to keep to themselves and how best to secure it.
  • ...10 more annotations...
  • more and more data are seeping out of companies, even of the sort that should be well protected.
  • To be able to work better with data, employees often transfer them into spreadsheets and other types of files that are easier to manipulate—but also easier to lose control of.
  • Although most leaks are not deliberate, many are.
  • “data loss prevention” (DLP).
  • software that sits at the edge of a firm's network and inspects the outgoing data traffic.
  • “bells in the dark”. False records—made-up pieces of e-mail, say—are spread around the network. Because they are false, no one should gain access to them. If somebody does, an alarm is triggered
  • In the corporate world, to limit the channels through which data can escape, some companies do not allow employees to bring their own gear to work or to use memory sticks or certain online services.
  • How then to strike the right balance between secrecy and transparency?
  • Intel, the world's largest chipmaker, issues “speeding tickets” to employees who break its rules.
  • Transparency is not just a natural inclination but a necessity, says Mitchell Baker, who chairs the foundation. If Mozilla kept its cards close to the chest, its global community of developers would not and could not help write the program. So it keeps secrets to a minimum: employees' personal information, data that business partners do not want made public and security issues in its software.
Joanne S

The Deep Web - 0 views

  • defined as the content on the Web not accessible through a search on general search engines.
  • sometimes also referred to as the hidden or invisible web.
  • the part of the Web that is not static, and is served dynamically "on the fly," is far larger than the static documents
  • ...11 more annotations...
  • When we refer to the deep Web, we are usually talking about the following:
  • The content of databases.
  • Non-text files such as multimedia, images, software, and documents in formats such as Portable Document Format (PDF) and Microsoft Word.
  • Content available on sites protected by passwords or other restrictions.
  • Special content not presented as Web pages, such as full text articles and books
  • Dynamically-changing, updated content,
  • let's consider adding new content to our list of deep Web sources. For example:
  • Blog postings Comments Discussions and other communication activities on social networking sites, for example Facebook and Twitter Bookmarks and citations stored on social bookmarking sites
  • Tips for dealing with deep Web content
  • Vertical search
  • Use a general search engine to locate a vertical search engine.
  •  
    The Web not accessible through a search on general search engines..
Joanne S

Is Internet access a human right? - Technolog on NBCNews.com - 0 views

  • when the Internet is taken away, as it has been in Egypt, people feel as though their rights have been stripped.
  • "If we can't communicate, we can't organize, if we can't organize, then we are reduced to power of a single individual,"
  • "There are certain technological advances that are such leaps forward in human evolution that they do, in fact, become human rights. Vaccines, for example. Potable water. I believe the Internet has become one as well."
  •  
    "In Egypt in early 2011, during the revolution the government cut off the internet between 27 January and 2 February. These links were shared by Farah, a previous student who was in Egypt during this period."
1 - 19 of 19
Showing 20 items per page