[
http://opencast.jira.com/browse/MH-6910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31401#comment-31401
]
Rubén Pérez Vázquez commented on MH-6910:
-----------------------------------------
Judy is replying to this Karen's mail (which I don't know why it does not made
it into the comments... does Karen has an account in JIRA?)
==============================================================================================
Judy,
What about the poor person that has to manually enter the same series and
recording requests data semester after semester after semester (until the
course gets dropped or its syllabus radically changes) through the Matterhorn
UI? Is it really fair to call that poor student aid worker a "metadata fanatic"?
Here is 2¢, if someone has time to make the page...
1) The page harvests series data (in a date range, or from the beginning of
time?)
..../series/series.xml?...
2) The page transform the series list xml into pretty HTML for click-able
selection.
3) User selects one of the series from the list. Now page show series metadata
in an editable form.
3.1) The page retrieves episode metadata to facilitate bulk Recording
scheduling.
... /episode.xml?series=[selected seriesID]
... Page also show list of series episodes.
... Page allows user to add and delete from the potential events and expand
episode meta data into editable form.
4) Administrator edits series and/or episode metadata.
... insert new series ID (or let Matterhorn create)
... add new recording dates, change titles...
5) After making edits, administrator clicks [create new series & schedule
recordings] button.
...Browser runs client side data validation before formatting data for POST and
MAKES SURE that user is not using an existing series ID(!!).
==============================================================================================
> As an administrator, I want to see and manage (sort, order, search) all the
> DC metadata files so I can re-use them for either adjustments or re-use
> (metadata templates)
> ------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MH-6910
> URL: http://opencast.jira.com/browse/MH-6910
> Project: Matterhorn Project
> Issue Type: Story Card
> Components: Architecture & Services
> Affects Versions: 1.2
> Reporter: Olaf A. Schulte
> Assignee: Christoph E. Driessen
> Fix For: Trunk
>
>
> In order to facilitate the allocation of metadata, the admin should have
> access to all the episode and series metadata files so they can be copied,
> enhanced and re-used. As most events are re-occuring, this should facilitate
> the admins work and make sure metadata are consistent over semesters etc.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://opencast.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
Matterhorn mailing list
[email protected]
http://lists.opencastproject.org/mailman/listinfo/matterhorn
To unsubscribe please email
[email protected]
_______________________________________________
