# data[].attributes.body
[Merge slides 2-4] Small introduction about pilots and the vision for improved module metadata infrastructure.

# data[].attributes.body
Brief introduction to metadata and an explanation of modules/module content metadata. Describing crucial aspects, Persistent identifiers etc.

# data[].attributes.body
High level overview of the most used production systems outlining metadata capabilities/usage of each system. Not sure how to present information on these systems; using a chart? spider diagram of how each production system interacts? Do we deliberately show how intricate and confusing this can be to suit the narrative of why proper metadata usage is important?

# data[].attributes.body
Demonstrate the current set up from Module Index; you cannot search across sites [video demo from module index]. Demonstrate lack of searchability with a few examples from systems we are able to access. 300+ live modules alone.

# data[].attributes.body
*changed to screenshot as we don't need two videos to illustrate this* Advise this is where most of the module content is expected to be. Predominant production system. Deeper dive into SharePoint as this is where the majority of learning assets are held. Illustrating what we've discussed in the previous slide. Mandatory fields not being filled in and no metadata related to the content. Only structural metadata. Can't search/discover content.

# data[].attributes.body
Video explains tags before screenshot of different module navigation menus (includes 7-11)

# data[].attributes.headline
Slide 7: Showing different navigation menus

# data[].attributes.subject
Slide 7: Showing different navigation menus

# data[].attributes.body
[Notes on slides]

# data[].attributes.body
Notes on slides. Shows how we can better utilise SharePoint

# data[].attributes.body
Brief introduction to structured authoring / use of mark up language allowing modules to render content to different formats.

Written in XML and rendered out to word, pdf, epub and HTML etc. to be delivered on whatever learning platform being used at the time so not reliant on recreating content multiple times for multiple formats.

XML is where course components are knitted together so when rendered those assets are pulled into whatever format you’re trying to create.

# data[].attributes.body
Screenshot of oxygen plus a rendered version in text, pdf or something else. Explain this is key to how production works.

# data[].attributes.body
screenshot of Pathway 1 and screenshot from Carly if possible

# data[].attributes.body
Minerva screenshot? Previous projects around direct authoring which is Minerva project is.

We’re interested to know what’s new in the direct authoring pilots [presentation on this in SharePoint so can have a look to see if we can utilize slides]

One of the pilots is about direct authoring; what is it about that that we think metadata may be utilized to improve or considered when thinking about undertaking it?

About audit and tracking changes with direct authoring.

They’re just not using metadata right now.

How they document copyright of new stuff and changes from point of view of university’s ability to show what a student has seen on a given day.

Students will/can challenge their grading based on content on the site. If we don’t have auditing we can’t evidence this.

# data[].attributes.headline
Slide 13-14: module structure and taxonomy

# data[].attributes.subject
Slide 13-14: module structure and taxonomy

# data[].attributes.body
Explain/show how proper use of metadata can break the silos of individual module SharePoint sites, module content becomes more accessible etc.
Wendy’s understand what the plans are so we can understand how this taxonomy can be embedded in the metadata making it easier to see and use.

At the moment it’s not embedded into any systems

We could embed it into SharePoint and make use of some of the legacy fields to do that maybe?

What is this first focus area? We can aid them by embedding it into the metadata of SharePoint.

Find out if they’re covering taxonomy at all on this module and understanding what they want from that so we can embed it into SharePoint.

Taxonomy is a key aspect we think we’d be able to help with – frame it this way for Wendy’s

Just a website currently not embedded as yet….we can help with this!