Saturday, January 24, 2015

Observations - The sizing needs to be adjusted on the columns The format for the REGISTRY_ID column appears to be an incorrect format. The annotation used makes all of the numbers the same on the sheet. Once I changed the format – I see that all of them are still the same. How useful is this ID if they are all the same? The phone numbers do not have any -‘s in-between the numbers. This makes them difficult to read. There are many blank or unknown fields. Many of the abbreviations are not intuitive to me. With no context; this makes it difficult to know what exactly this data is for. The data does not appear to be in any particular order – not alphabetical, numeric or chronological. How to make sense of this data Part one – assuming that context cannot be found for this data. Since there is no context and the abbreviations are not intuitively understood – I feel that the best way to make sense of this data is to organize it based on the dates. I would sort the data starting with the oldest entry without an end date, followed by ones with the most recent end date. The decision to organize this list as such is an educated guess on my part. I assume that the dates are the most important data (do to a lack of understanding of some of the data) and further assume anything that is old and does not have an end date would represent an active acct with much history; thus need to be most easily accessible at the top of the list. Entries with recent end dates may represent a customer at risk or a person would may want to renew some sort of license. Another method would be to import this Excel sheet into Access. Whereas Excel is little more than a list – Access is a data base that would allow for more functionality where it comes to searching for any of the data in this sheet. Part two – a search for context. I went to data.gov and used their search and filter functions in an attempt to obtain context for this data. Despite searching for several of the data from the Excel sheet; I was not able to find this particular sheet on the site; thus was unable to obtain the contextual information that I thought would help determine how best to make sense of this data.

No comments:

Post a Comment