Week 4 – Reflection

 

Information Overload

The management of digital heritage is definitely becoming more of a concern today then ever before. The problem I feel with digital heritage is that there is just too much. In the past where physical objects would get destroyed due to age, deterioration, handling etc., the collections of heritage available for preservation would get smaller per subject field as time goes on. When it comes to digital heritage as time goes on, the accumulation per subject field becomes more.

It is lovely to save everything but perhaps like trying to save everything in a fire we need to let some things go. As well as a system designed for improving data management we also need a system to dispose of data. Perhaps we could employ a bot for the job?

I had a go a creating a graph using Plot.ly this week. It absolutely looks no different to the graph from the tutorial however I did make this one all by myself, from scratch. #proudmoment Embedding the graph was easier said then done. Firstly, one must enable the private share link and secondly since I have coded this weeks blog in the text format, I needed to change the embedding code from an ‘iframe’ to ‘html’. I also decided we needed some style and colour on this blog page. Note: my coding skills are young and fresh with much to be learnt so basic coloured headings and some font change is all I could achieve for this week.

A Plot.ly Graph

1901 Census: Population of South Australia (except Adelaide)