[ACTION-20] Gather CMS user and developer perspective requirements from MLW-LT, including from drupal con

Hello all,

 

I had an action item due today: 

ACTION-20: Gather CMS user and developer perspective requirements from
MLW-LT, including from DrupalCon

 

Here's what we've collated this far. As we are still receiving information
every once in a while, so I'll update when we have even more information.

 

Cheers,

Moritz


Content workflow metadata
Metadata relevant for content managers and/or localisation managers should be
made transparent. CMS should be able to adapt the presentation of those
metadata which are relevant to the specific needs of the client. An example
could be the revision and clearing of content translations. A sample use case
for relevant metadata might include among others:

1.	translation type (HT, MT, FHQT, ...)
2.	type and degree of QA (post-edited, checked by legal, ...)
3.	revision information (these may include process trigger and process
state information)
4.	localisation note(s)
5.	language ID(s)

Technical content processing metadata
The CMS must be able to preserve and save metadata within the system. Any
components and functionalities which modify content shall not discard
metadata. This includes the transformation of metadata from CMS-intrinsic
formats into other formats and vice versa. This requirement extends past
those metadata with which content manager and/or localisation will deal with
directly and therefore applies to all MLW-LT metadata.
Content identification metadata is also needed, e.g.:

1.	content identifier
2.	revision identifier
3.	source and target (languages)

Identification information may be highly CMS-specific. This information is
also needed for the re-integration of content as it comes back from the LSP.