New "Assets" or "Resources Model for Consideration

[alyciapiazza]

Hi team - We have a challenge that I hope you all can help with. Since the development of DigitalGov.gov we realize that a lot of the resources</a href> (laws & regs/guidelines, tools and reference materials) we’ve curated and provide to agencies:

• aren't always owned by us (we link to laws / memos on OMB, WH etc)
• aren't (in a lot of cases) able to be searched (pdfs / docs)
• are popular and not easily findable
• are in need of better organization
• and / or a combination of these

We have been calling these bits of information “assets” and they include: documents, pdfs, powerpoints presentations, video, audio, photo, and outside links to these same items.

We took a stab at creating a template and realized that we were creating "fields" and essentially it could be a content model. We looked at the current article and we don’t think that it applies in this situation.

I have talked this through with @jpgsa and he suggested I take a look at Schema.org to see if there is an equivelent. It occurs to me that the Creative Works</a href> model or perhaps more specifically the Media Works</a href> (specific types below) might work well.
More specific Types:
AudioObject</a href>
DataDownload</a href>
ImageObject</a href>
MusicVideoObject</a href>
VideoObject</a href>

Ultimately, we envision a page for each asset with the minimal but most important information for the customer, tag the page, and use feeds and queries to pull the information via "search" specific and unique to the assets.

Does anyone have a similar approach or need like this? Also, just throwing it out there, do you all think this would be a good government-wide model?

Please let me know if you have questions about what we are trying to do.

[dwagner4]

We have pondered the same problem and have the need, regretfully no
solution. Both public facing information and internal records could
benefit from uniform schema across the government and it would be a good
practice. Serving the public, eDiscovery and FOIA also mandate the ability
to find assets accurately and efficiently. We see a need for three
functionalities.

• uniform metadata (a la schema/models)
• full text search
• links to related assets (as in a graph database)

One barrier is efficiently registering new assets and migrating existing
assets to the new schema. Many fields makes the problem worse.

Dean Wagner
[email protected]

On Fri, Nov 7, 2014 at 12:23 PM, alyciapiazza [email protected]
wrote:

Hi team - We have a challenge that I hope you all can help with. Since the
development of DigitalGov.gov we realize that a lot of the resources
http://www.digitalgov.gov/resources (laws & regs/guidelines, tools and
reference materials) we’ve curated and provide to agencies:
aren't always owned by us (we link to laws / memos on OMB, WH etc):

• aren't (in a lot of cases) able to be searched (pdfs / docs)
• are popular and not easily findable
• are in need of better organization
• and / or a combination of these

We have been calling these bits of information “assets” and they include:
documents, pdfs, powerpoints presentations, video, audio, photo, and
outside links to these same items.

We took a stab at creating a template and realized that we were creating
"fields" and essentially it could be a content model. We looked at the
current article and we don’t think that it applies in this situation.

I have talked this through with @jpgsa https://github.com/jpgsa and he
suggested I take a look at Schema.org to see if there is an equivelent. It
occurs to me that the Creative Works http://schema.org/CreativeWork
model or perhaps more specifically the Media Works
http://schema.org/MediaObject (specific types below) might work well.

More specific Types:
AudioObject http://schema.org/AudioObject
DataDownload http://schema.org/DataDownload
ImageObject http://schema.org/ImageObject
MusicVideoObject http://schema.org/MusicVideoObject
VideoObject http://schema.org/VideoObject

Ultimately, we envision a page for each asset with the minimal but most
important information for the customer, tag the page, and use feeds and
queries to pull the information via "search" specific and unique to the
assets.

Does anyone have a similar approach or need like this? Also, just throwing
it out there, do you all think this would be a good government-wide model?

Please let me know if you have questions about what we are trying to do.

—
Reply to this email directly or view it on GitHub
#10.

[hbirving]

I think the Article model might work for documents if the ArticleType field were used to describe the function/purpose of the item and provide context for how the item is used. For example:

1. http://www.digitalgov.gov/services/dap/dap-digital-metrics-guidance-and-best-practices// might be tagged "guidance" and "best practices"
2. http://www.digitalgov.gov/resources/spanish-language-style-guide-and-glossaries/spanish-health-care-terms-in-the-united-states/ might be tagged "glossary"
3. http://www.digitalgov.gov/files/2013/11/Social-Media-Fed-Govt-Barriers-Potential-Solutions.pdf might be "report"
   To be consistent I think it would be useful to use a similar field for the Media Works. A video for example could be used for instructions, or as a promotional piece, a legal warning or disclaimer, etc.
   There are some standard vocabularies around especially in the library community that could be used for this purpose and I think a standard list would be very useful.

I did some poking around in schema.org and the content type I couldn't find is for "index pages" or "landing pages" that serve the purpose of pulling together links to resources around a topic like the Resource page on Digitalgov or this one: http://www.digitalgov.gov/resources/spanish-language-style-guide-and-glossaries/ Could that be a content type worth considering as well?

The data.gov schema might work for datasets.

While tempting, IMHO the responsibility for tagging lies with the author/source. schema.org does have models for URLs, but I'm not sure we want to get that detailed.

I think a need some help understanding what you have in mind, particularly regarding a page for each asset. So it's possible I'm completely off course with my comments

[jpgsa]

11/19 Working Group Meeting Notes
Holly reiterated her questions above.
Potentially multiple content types involved instead of a overarching content type (video, audio, subtype of infographic,etc.) Use a content type, that's just an external link--one place to maintain? Schema.org URL?
Example of Digital Assets model?