Skip to content
This repository was archived by the owner on Jul 24, 2025. It is now read-only.

Webspace for multimodal resources #284

Description

@IAlferink

As part of our pedagogy we want to offer learners multimodal materials, meaning they are exposed to language input in two modalities at the same time. For example, hearing audio and having the text appear simultaneously. Giulia has created an example for us.

We need a webspace for these resources as well as a workable workflow.

I'm copying the information from our e-mail exchange on this:
Do you know how many audio files would be required and what will be total listening time? This can help estimate the size of the storage although this is cheap and easy to organise.
We're expecting a maximum of 3 audio files (one per language) totalling  7.5 minutes per teaching week (40 per year) for Year 7 and Year 8 and a maximum of 3 audio files )one perlaguages) totalling 15 minutes per teaching week for Y9. These will gradually be added over the course of the next two years.

How do you plan in the future to load new content (both audio and annotated text layer), will this be one person or multiple diverse userbases (e.g. web admin, teachers, academics)? 
We expect a fairly regular drip of these and wouldn't want to put more pressure on your already limited time, so I think the NCELP team should be able to load new content. We could either designate a team member for each language or have all resource developers and resource assistants do it.It would be nice if teachers could use it too, but not essential as they could go through CELP. How we can set this up is a question for you.

How do you expect the users/students will access the collections of audio playing files? What devices phones? or classrooms screens? What another search, organise functionality you might have?
Links to the pages will be added to our teaching materials and users will access the pages through this. I imagine this typically be classroom screens and occasionally phones. So, I don't think we need to worry about organise or search functionality as they won't be stand alone, but linked to other resources.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions