The Effects of Computer Use on Eye Health and Vision
Source:
American Optometric Association.
www.aoa.org/documents/EffectsComputerUse.pdf. Retrieved Sept 24, 2009.
Abstract
The article discusses the hazards people face when working on computers. These hazards can range from eye and vision related discomfort, neck and back pain, to possible exposure to light radiation from computer monitors. These problems can be addressed by proper workplace lighting to improve contrast between screen and the user’s surroundings. Proper egronomic design of the workstation can help ease neck and back discomfort. Occasional breaks to allow employees rest from continuously looking at computer monitors. These risks and possible solutions are currently being researched by The American Optometric Association.
3 Things I’ve Learned
1. Improper office design can lead to injury such as impaired vision and neck and back pains
2. Working with computers and the harm that can be garnered from it reduces productivity.
3. Effective planning and design of the workplace and proper consideration of worker welfare can greatly reduce these risks.
Reflection/Application
As a librarian, even though my role revolves around books, computers have been an essential part of my daily activities. It has replaced numerous traditional systems. The information I have obtained from the article will help me avoid risks that could cause problems to my eyesight, neck and back. I could also use this knowledge to design better workspace for the library clientele, mainly for those who may use computers or audiovisual equipment.
Friday, September 25, 2009
Friday, September 18, 2009
RA 9 : Rules of Court on Electronic Evidences
Rules on Electronic Evidence
Source: http://nationallibraryphilippines.wikispaces.com/file/view/Court+Rules+on+Electronic+Evidence.pdf. Retrieved on Sept 16, 2009
Abstract:
This article discusses the Philippine law on rules of court on electronic evidences. There are twelve rules that were included in this law namely the coverage, definition of terms and construction, electronic documents—best evidence rule, authentication, evidentiary weight, on audio, photographic, video, and ephemeral evidence and its effectivity.
Electronic document and data message and can be used as evidence the same as the one written in paper or the original document. Duplicates and copies are also regarded as equivalent of the original. Authenticity is just the question. The person seeking to introduce an electronic document in any legal proceeding has the burden of proving its authenticity.
3 Things I’ve Learned:
1. An electronic document shall be regarded as the equivalent of an original document under the Best Evidence Rule if it is a printout or output readable by sight or other means, shown to reflect the data accurately.
2. “Asymmetric or public cryptosystem” means a system capable of generating a
secure key pair, consisting of a private key for creating a digital signature, and a public key for verifying the digital signature.
3. “Digital Signature” refers to an electronic signature consisting of a transformation of an electronic document or an electronic data message using an asymmetric or public cryptosystem such that a person having the initial untransformed electronic document and
the signer’s public key can accurately determine: (i) whether the transformation was created using the private key that corresponds to the signer’s public key; and,
(ii) whether the initial electronic document had been altered after the
transformation was made.
Reflection:
I’ve learned so much with this reading assignment. What is more interesting is it is also written within the Philippine law context. In our everyday life, we use e-mails, text messages, photos and videos as part of our work, studies, or just simply documenting what is happening in our lives. These documents also serve as evidences when it comes to legal issues/court cases, the only question is its authenticity. As a librarian and student, it is very important that we secure all our documents whether in electronic and paper format. We must learn from the mistakes of other people who were involved in scandals, and legal cases because such electronic evidences were presented in the court.
Source: http://nationallibraryphilippines.wikispaces.com/file/view/Court+Rules+on+Electronic+Evidence.pdf. Retrieved on Sept 16, 2009
Abstract:
This article discusses the Philippine law on rules of court on electronic evidences. There are twelve rules that were included in this law namely the coverage, definition of terms and construction, electronic documents—best evidence rule, authentication, evidentiary weight, on audio, photographic, video, and ephemeral evidence and its effectivity.
Electronic document and data message and can be used as evidence the same as the one written in paper or the original document. Duplicates and copies are also regarded as equivalent of the original. Authenticity is just the question. The person seeking to introduce an electronic document in any legal proceeding has the burden of proving its authenticity.
3 Things I’ve Learned:
1. An electronic document shall be regarded as the equivalent of an original document under the Best Evidence Rule if it is a printout or output readable by sight or other means, shown to reflect the data accurately.
2. “Asymmetric or public cryptosystem” means a system capable of generating a
secure key pair, consisting of a private key for creating a digital signature, and a public key for verifying the digital signature.
3. “Digital Signature” refers to an electronic signature consisting of a transformation of an electronic document or an electronic data message using an asymmetric or public cryptosystem such that a person having the initial untransformed electronic document and
the signer’s public key can accurately determine: (i) whether the transformation was created using the private key that corresponds to the signer’s public key; and,
(ii) whether the initial electronic document had been altered after the
transformation was made.
Reflection:
I’ve learned so much with this reading assignment. What is more interesting is it is also written within the Philippine law context. In our everyday life, we use e-mails, text messages, photos and videos as part of our work, studies, or just simply documenting what is happening in our lives. These documents also serve as evidences when it comes to legal issues/court cases, the only question is its authenticity. As a librarian and student, it is very important that we secure all our documents whether in electronic and paper format. We must learn from the mistakes of other people who were involved in scandals, and legal cases because such electronic evidences were presented in the court.
Friday, September 11, 2009
RA 8 : Open Source Software
Issues of Dependability in Open Source Software Development
Lawrie, Tony (May, 2002). Issues of Dependability in Open Source Software Development. Retrieved Sept 10, 2009 from http://delivery.acm.org/10.1145/640000/638584/p34-lawrie.pdf?key1=638584&key2=0798262521&coll=ACM&dl=ACM&CFID=51206778&CFTOKEN=14041621
Abstract:
The article “Issues of Dependability in Open Source Software
Development” discusses many aspects of Open Source Software revolving
around its dependability and the processes that contribute to that
dependability. To the author, dependability as discussed pertains to
reliability, security and safety of these processes.
First, it discusses the dependability of OSS products. Software
developed as Open Source needs to maintain attributes such as
security, reliability and availability to be called dependable. It
also makes comparisons between Open Source and Non-Open Source
Software Development, citing that the former is not necessarily more
dependable than the latter and gives examples of scenarios where OSS
is at a disadvantage.
Then it discusses the dependability of OSS Processes. It mentions that
OSS processes are less constrained compared to Non-OSS ones because
commercial, time and political barriers apply less. Also, OSS codes
are exposed to higher level of reused and increased knowledge
accumulation is promoted. It mentions that increased potential for
diverse collaboration is found in communities practicing OSS
development.
Issues and implications for OSS and Dependability were also discussed.
It states that there is a need to determine at which attributes assure
dependability of both OSS and Non-OSS software and the evidence that
leads to these conclusions. The nature and type of products, business
and government attitudes, and the tools and paradigms that these
approaches use are to be taken into consideration. Even with the
obvious differences, the article states that there is no substitute
for human intelligence in the development process.
As a conclusion, the author states that OSS products may be limited to
the development of systems oriented software which is vital for
further trustworthy composition and building of dependable systems.
The OSS approach is not subjected to the same of constraints like time
and budget. Tools and methods will contribute to the drive to improve
process and quality assurance.
Three things I learned from the Article:
1. Open Source Software products and processes are less limited by
time and budget constraints compared to Non-OSS software.
2. Tools and Processes do a lot to improve Open Source development
even if they lack the resources in comparison to Non-OSS development.
3. Dependability can be defined under a number of things, such as
reliability, availability, security, and even the perception of the
users.
Reflection:
As a librarian I can put to good use these practices discussed in the
article. While I recognize that I work under a government institution
such as Engineering Library II which at times can be subject to
limitations such as manpower or budget constraints, it is by no means
an excuse not to provide dependable services to our clients. What we
can do is to improve our processes the same way these OSS developers
have done to get around these limitations. We can also establish
better tools such as better indexes and loaning protocols so as to
enhance the security of our materials without subjecting our clientele
experience to less than satisfied. We can also establish relationships
with other libraries as a collaborative effort to provide information,
the same way boundaries were not considered in OSS developers efforts
to create their products.
Lawrie, Tony (May, 2002). Issues of Dependability in Open Source Software Development. Retrieved Sept 10, 2009 from http://delivery.acm.org/10.1145/640000/638584/p34-lawrie.pdf?key1=638584&key2=0798262521&coll=ACM&dl=ACM&CFID=51206778&CFTOKEN=14041621
Abstract:
The article “Issues of Dependability in Open Source Software
Development” discusses many aspects of Open Source Software revolving
around its dependability and the processes that contribute to that
dependability. To the author, dependability as discussed pertains to
reliability, security and safety of these processes.
First, it discusses the dependability of OSS products. Software
developed as Open Source needs to maintain attributes such as
security, reliability and availability to be called dependable. It
also makes comparisons between Open Source and Non-Open Source
Software Development, citing that the former is not necessarily more
dependable than the latter and gives examples of scenarios where OSS
is at a disadvantage.
Then it discusses the dependability of OSS Processes. It mentions that
OSS processes are less constrained compared to Non-OSS ones because
commercial, time and political barriers apply less. Also, OSS codes
are exposed to higher level of reused and increased knowledge
accumulation is promoted. It mentions that increased potential for
diverse collaboration is found in communities practicing OSS
development.
Issues and implications for OSS and Dependability were also discussed.
It states that there is a need to determine at which attributes assure
dependability of both OSS and Non-OSS software and the evidence that
leads to these conclusions. The nature and type of products, business
and government attitudes, and the tools and paradigms that these
approaches use are to be taken into consideration. Even with the
obvious differences, the article states that there is no substitute
for human intelligence in the development process.
As a conclusion, the author states that OSS products may be limited to
the development of systems oriented software which is vital for
further trustworthy composition and building of dependable systems.
The OSS approach is not subjected to the same of constraints like time
and budget. Tools and methods will contribute to the drive to improve
process and quality assurance.
Three things I learned from the Article:
1. Open Source Software products and processes are less limited by
time and budget constraints compared to Non-OSS software.
2. Tools and Processes do a lot to improve Open Source development
even if they lack the resources in comparison to Non-OSS development.
3. Dependability can be defined under a number of things, such as
reliability, availability, security, and even the perception of the
users.
Reflection:
As a librarian I can put to good use these practices discussed in the
article. While I recognize that I work under a government institution
such as Engineering Library II which at times can be subject to
limitations such as manpower or budget constraints, it is by no means
an excuse not to provide dependable services to our clients. What we
can do is to improve our processes the same way these OSS developers
have done to get around these limitations. We can also establish
better tools such as better indexes and loaning protocols so as to
enhance the security of our materials without subjecting our clientele
experience to less than satisfied. We can also establish relationships
with other libraries as a collaborative effort to provide information,
the same way boundaries were not considered in OSS developers efforts
to create their products.
Friday, September 4, 2009
RA 7: Field Trip to IRRI
*photo courtesy of Jhoanne
Last August 26, 2009 our class had a field trip in IRRI (International Rice Research Institute) in UP Los Baños Laguna. The aim of the field trip is to expose the students to the latest development of library and information science. The lecture/orientation was given by Ms. Mila Ramos, chief librarian with Ma’am Ems and Ma’am Lea, senior librarians. They talked of their services focusing mainly on CAS, SDI and document delivery. Document delivery (electronic and conventional) is a fee based service for faculty, students and staff of the university. Yet in IRRI, document delivery is free to scientists up to 50 pages. And for other users, the fee will be only based on the cost of the photocopying of the material. They also gave a description on their library system which is the Millenium (very costly) particularly the Circulation, Cataloging and Serials modules. The librarians also discussed about the access points of the electronic journals.
Three things I’ve learned:
1. Librarians are very resourceful in serving their clients better. They make a system on how to retrieve and get information for clients that organized, user-friendly and consistent like in the access points of electronic journals.
2. Web 2.0 applications are very effective ways to reach out to the library’s clients like blogs and chat service. They serve clients all over the world with different time zones yet the librarians are very reliable because users are their priority.
3. Open access journals that are selected and evaluated by the librarians are great help for additional information of researchers. They are free and openly available for public use.
Reflections:
It gave me a fresh perspective on how new technologies can be used to improve the library I maintain now. Moreover, one cannot overstate the value of experienced librarians such as those maintaining the IRRI library. They have showed me that even though I have been a practicing librarian for almost two years and I am immersed in new trends in the profession I feel that there is still much to learn particularly on the foundation skills on which the practice of librarianship is built upon.
Subscribe to:
Comments (Atom)
