# Metadata on the LMEC Public Data Portal
- Let's take a look at the metadata which we created for the Internet Access in Boston data
- (That's the dataset that was used to create this map that we've seen before)
# About This Data
Problem: Sometimes you just want some quick facts at a glance about a dataset, without having to download or open the data.
Solution: The "About This Data" section of the page includes an overview or description of the dataset. In addition to basic descriptive information like the key attributes and access conditions, it includes:
- What topics or themes does the dataset address?
- What time period does the dataset cover?
- Where in the world does the dataset represent?
- Many, but not all, datasets on the LMEC portal are about Boston!
- Who originally collected and cleaned the dataset?
- Why is it archived in the LMEC portal?
# Example
# Get This Data
Problem: Sometimes it can be confusing how to get access to the "raw" data files. Sometimes you want to download the data, sometimes you want to preview it. Lots of different format options seem complicated.
Solution: The "Get This Data" section of the page:
- Is prominently featured to provide quick access
- Provides links to documentation on different file formats
- Tags options as "suggested" if there are multiple formats available
- Allows for both full-access downloading, but also previewing in the browser, using geoJSON.io
# Example
# The Data Lifecycle
Problem: It can be challenging sometimes to understand how a dataset came to be. Who manipulated it? What tools did they use? What was the reasoning behind their process?
Solution: The "Data Lifecycle" section of the page provides links to the records of those who have worked with data, describing, in their own words, their steps and choices.
You will not find this information in most data portals. It is an excellent way to understand how the data has been shaped, and by whom. You can also use this section to reproduce the steps of the original data processor, if necessary.
# Example 1
# Example 2
# Data Genealogy
Problem: It can sometimes be challenging to understand how a dataset came to be. Was it derived or combined from other data sources?
Solution: The "Data Genealogy" section of the page:
- Links to all source datasets
- Provides a step-by-step breakdown of how the dataset was created
# Example
# Related Resources
Problem: Datasets alone, without context, are hard to use. A lot of the time, there are useful supplementary resources that can help us understand more about a dataset.
Solution: The "Related Resources" section of the page links out to helpful:
- Documentation
- Codebooks
- Articles
- Blog posts
- Other publications
- Supplementary files
- Maps made from the data
- And more...
# Example
# Considerations
Problem: Sometimes, even when factual information is available about a dataset, it can still be difficult to make sense of the dataset's usefulness to your question or project.
Solution: The "Considerations" section of the page give you clues about:
- How well this dataset has been described so that people can understand it
- How easily compatible with GIS software and other computer programs the dataset is
- How thorough the documentation is in describing the dataset's social context
TIP
For more information about this process check out considerations documentation.