Unit 11

When I began this course, I had never even heard of Linux or a command-line interface. I have to admit that I felt fairly out of my depth, but I am enthusiastic about learning new things and technology is an area where I would especially like to strengthen my knowledge. I have also genuinely enjoyed learning about these topics, and it has been exciting to have those moments when something finally "clicks."

I have worked hard at the concepts and feel that I now have at least a basic grasp of the command-line interface as well as how it differs from a graphical user interface, what Linux is and how it differs from other operating systems, what a web server is, how to create a web page with HTML, what XML is and what it is and isn't used for, how to develop a database, as well as a myriad of other technical information. I particularly enjoyed learning HTML and MySQL, perhaps because it was fun to see the immediate outcome of using them.

On a deeper level, I now understand so much more about why these different technologies are used and how they fit together in order to build a complex digital collection. It has changed my perception of digital collections being things that I could only hope to work with as an end-user, to seeing that I could learn how to work with them at a deeper level. It was helpful to be able to see the inner workings of a digital database. I am very grateful that I took this course and am really looking forward to 675 next semester. I can't believe how much I have learned in the last couple of months and how far my technical knowledge in general has grown.

Unit 10

This week's assignments were very intense for me, and took me a very long time to get my head wrapped around (thus the slightly late post). At the same time, it was one of my favorite topics of the course. The most difficult concept for me to understand was the queries, especially the left join/right join. However, having to come up with my own for the weekly dropbox assignment really forced me to look at it closely and mull over the differences between the different joins, and I am happy to say that I now understand them (at least on a basic level).

At first the MySQL syntax was a little but overwhelming to me, but the more I do it the easier and more intuitive it becomes. I really look forward to creating a couple of my own databases and playing around with them. I would like to create one for my home book collection, as well as one for my small art business. I found myself liking MySQL for laying out database and table structure, then using Webmin as a way to add values to the database tables. It seems like a simple way of adding information. There were a couple of times this week where I felt overwhelmed by all of the new information, but in the end I feel like I learned a lot of extremely useful information.

Unit 9

This week we learned about data modeling and proposed a simple database based on our previously created XML document. I really enjoyed learning about this; I felt that the basic concepts were accessible and very immediately useful. I had learned a little bit about entity relationship diagrams in IRLS 515, but felt that I was able to get a deeper understanding of it this time around.

I felt that I gained a good understanding of the crow's foot notation after spending some time on it, as well as a pretty good understanding of the differences between entities and attributes. The thing I am still having a hard time with is how everything goes together in the diagram when you have several or many entities/attributes. I also was only able to grasp a basic understanding of database normalization. I really look forward to learning more about this topic; I have a small business of my own that I would like to create a database for, so that gives me extra motivation to try to understand these topics.

Unit 8

This week we did a lot of reading about technology plans for libraries. I was not aware of technology plans and found it to be quite interesting and helpful to learn about. I noticed some common advice in the readings about what a good technology plan should consider and include:

• the plan should be based upon the organization's overall mission
• users should be the main focus
• the plan should have top management involvement and support
• involve as many stakeholders and end users as possible
• recognize that technology is a means to an end, not an end in itself
• the plan should be a living document and updated often

I looked closely at two technology plans from Connecticut libraries, one from the Avon Free Public Library and one from the West Hartford Public Library. I thought that they were both quite good and were very similar in structure: they each included a technology vision statement, a description of the current technology environment in their libraries as well as their specific needs, their goals with the technology, as well as general plans for staff training and evaluation. I felt that they were thorough yet concise.

I do believe that any networking will be valuable to me in assisting in technology planning in my future career. I believe that a technology plan would be useful to any organization, and having a background knowledge in technology would help in assessing the needs of the organization, as well as how those needs relate to its the goals and mission.