Skip to content

2. Data Structure

Flindy Ly edited this page Feb 23, 2023 · 1 revision

Loose thoughts around what the data should be at a minimum and in a way that is workable:

Each Media item would be an entry into the database.

Media Item

  • MediaItem: uid (retrieve from Box folder)
  • Type: array[shortcode] User input and selection - all items
  • Title: string (User input)
  • Keywords: array[string] (User input)
  • Contributor: string (Email)
  • School/Department: array[string] User input image/interactive
  • Thumbnail: upload
  • image: AI, PS, SVG, EPS User input video/animation
  • YouTube link: url
  • AE, PR, MP4, GIF, MP3 System details
  • visitCount: int
  • Date: timestamp
  • Published: boolean (false by default)

Album (Collection)

  • Title: string
  • Items: array[mediaitem]
  • Thumbnail: link (from Cloud Storage)
  • Type: string (Course, Group)

Type+Tags

(using shortcodes to make sub-selections: eg. vid-dro, vid-loc)

Video

  • Learning Video, Interview, Drone, 360, Location, Lab, Screencast, Case Study, Documentary

Image

  • Photo, Graphic, Illustration, Infographic, Graph, Flowchart

Animation

  • Gif, Narrated, Infographic, Storytelling, Case Study

Interactive

  • H5P, Custom, Reflective Practice, Storyline, Scenario Based, Drag and Drop, Quiz

Clone this wiki locally