# data[].attributes.body
1. How do we decide as a group when a tool has become stale?
2. How do we as a group decide when we add a tool?

# data[].attributes.headline
Are we missing a possible audience if  the list excludes iOS?

# data[].attributes.subject
Are we missing a possible audience if  the list excludes iOS?

# data[].attributes.headline
Process for fixing broken links INSTANTLY

# data[].attributes.subject
Process for fixing broken links INSTANTLY

# data[].attributes.body
Has to be a communal effort. To much information for even a small group. Maybe a report button to help identify changes in web places or policies that cause changes in use.

# data[].attributes.body
How to get content based teachers to recognize the transferable skills within their subject areas

# data[].attributes.body
hardware capabilities

# data[].attributes.body
Management and structure on management as resources and tools change.
Integrating & embedding vs just using tech
Dealing with tools that require age limits
Making it accessible across the state
The cost of tools (should it be a focus on OER)

# data[].attributes.body
How to move from substitution to transformation

# data[].attributes.body
Finding a way to make it continually relevant and match to EQS, etc. as that evolves.

# data[].attributes.body
add multiple tags ie.
primary TS
secondary TS
or content
and not searchable

# data[].attributes.body
1. Costs
2. Terms of Service age requirements
3. Maintaining list of ever-changing resources
4. Finding the "best" of so many tools

# data[].attributes.body
Managing how this not be just a list of tools for educators--buy in low if it becomes that.

# data[].attributes.body
1. School firewalls (edpuzzle won't work at SHS, for example)
2. Reluctant educators
3. Staying up to date with dizzying speed of tech progress