TH03-EP01-US001 - Media Management, Media Upload, Media Item Fields (Groomed BE21, FE8)... - 0 views
-
Media Management,
-
upload a new media item
-
syndication and encoding - not part of this user story
- ...26 more annotations...
-
definition
-
-
Owner
-
Rights of owner
-
dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now
-
-
Rights expiry date
-
dependent on implementation of licensing/rights management system which is tbd, so these will be best guess stubs for now
-
-
Syndication
-
dumbed down, feature parity implementation is just a list of idss allowed distribution (i believe) use existing legacy infrastructure? ultimate syndication system will depend on: - licensing - explicit list of syndication channels (much like legacy) - rule-based routing
-
-
Caption
-
Category
-
-
Seasonality display rules
-
this is one (simple) example of rule-based syndication: rule type: temporal (which could include: time range, recurrence, end time, etc) rule: syndicate while startDate>=now() and endDate<=now()
-
-
Short description
-
Long description
-
Search keywords
-
Associated with
-
-
in the media library
-
can be viewed by users
-
not only new ecm users, but legacy viewers as well ie. content uploaded via ecm must be available for display in legacy viewers, at least until legacy system is replaced and shutdown for good
-
-
Uploaded by
-
Date uploaded
-
Date modified
-
Last modified by
-
Status
-
TO DO: for new domain model, should define explicit content life cycle with state diagram
-
-
File type
-
Media type
-
Dimensions
-
Aspect ratio
-
aspect ratio doesn't need to be stored in db as metadata, since it can be calculated cheaply based on the dimensions
-
-
File size
-
-
File name
-
is this the original name of the file that was uploaded? if not, and it supposed to be the medlib file name, imho, should not be exposed. the medlib file name should be immaterial to the ecm user and generally, vfml should treat them as opaque to allow future changes without customer dependencies the only time an ecm user should care about a 'file name' is when they're uploading or downloading. but... once the file is uploaded, who cares what the original file name was? it will be recorded, but should be inconsequential to anything since it would never, ever be referred to again on download, (save as...) the original file name *could* be used, but any file name is just as good, since the downloader would also be given the option to rename the file
-
-
Media units consumed
-
calculated/cached value pull from legacy system in future sprints, could start to build phased shell of the marketing xxx system 1. getMediaUnits()
-
TODO: confirm with david and/or henry.wu where/how to obtain 'media units consumed' for a media item
-