Multimedia SUCKS!

[katster]

Alright, I'll ask this question generally, since somebody might be of help.

I'm trying to design a possible library application for film clips, for high school students working on a video yearbook. And I'd like the metadata stored on each clip to be well thought out, if not exhaustive, and that's why I need this data. So if you were working on a project, and wanted data about a video clip or still shot, what would you want to know about the clips?

Here's what I have so far:
ClipTitle, CameraType, Filename, Still/Video, Audio, PlaceTaken, DateTaken, TimeTaken, Duration, Hierarchy (for Hierarchy viewing mode), TypeofShot, Wide/Close, Cameraperson, Resolution, WhosInShot, FileType, Codec, BitRate, Size, Quality, FPS, UseInProject, DescriptionofClip, CompressedVideo.

If you can think of any others, let me know. I won't ink my drawings until tomorrow morning, and adding things to the database shouldn't be a big deal. Thanks.

Comments

[lirazel.livejournal.com]

You know, my company makes a product that does this... Not for film, but it can store images and could be adjusted to capture all of that.

You probably want to add some kind of unique identifier (it's possible that a clip could have the same name as another clip), and perhaps something that tracks changes. I mean, if someone edits it and puts it back, you'd want to know that, right?

You probably want at least two states for a clip to be in; in-work and released are the most common. Releasing something can trigger other events, like making the file read-only.

I don't want to burden you with all the hoo-ha in our product, which is meant for managing really complicated CAD assemblies, in all possible product configurations, as these change over time. But yeah, you have (or will have) captured What it is, Who made it, How did they make it, Where does it fit, Is it ready yet, and a few more...