This question comes in from Vanessa in Columbus, Ohio:
Do you have a definition guide with examples of what to put in each of the fields?
The quick answer is that there is no “Definition Guide” yet, as such. But if you’re looking for examples for each of the Suggested Metadata fields listed in Version 1.0 of the Digital Learning Asset Framework, then this video should do the trick.
Each of the metadata fields are simply suggestions, use what fits for your organization, and don’t use what doesn’t. Whatever naming conventions you may have for how assets or different version of assets are titled, keep that. Whatever data formatting makes sense to your team, do that. Whatever means you may have for identifying and tracking specific groups/audiences, yes to that.
And if you don’t have these things in place yet, don’t worry about it. Begin now, tweak later.
The most important thing with any of the metadata fields is that you have what you know you will need later.
- Who is this asset designed for? (the target audience)
- What problem is it designed to solve for those people? (the need)
- How will you search for this asset 6-months from now?
- What pieces of the puzzle might you be missing when it comes time to reversion this asset?
- Who signs off on changes to this asset?
- If this asset were to be retired & removed, what else would need to change too?
As more and more people answer questions like these for their content, and adopt the Digital Learning Asset Framework to pull their answers together, we hope to see new examples coming in. With each implementation, the Framework should grow stronger.
Version 1.0 is not meant to be the only version or the “we thought of everything” version. It’s meant to be a beginning, a place to start figuring out what really matters and to practice working with it. You may find that you want many more metadata fields than are provided now, great! You may find you need way less, great! Share what works and what doesn’t in your specific and unique environment, and compare notes with others who do the same.
This is how we collectively improve. Thanks for being part of the conversation!
More questions? Please use the comments below to submit what’s on your mind, and maybe you’ll see a post like this one written up in response 🙂