270 likes | 376 Vues
Discover the key functionalities of the CoolStateLA Converged Newsroom System, designed to streamline media management and story production. This system supports roles such as Reporter, Editor, and Assignment Editor, offering tools for proposing, assigning, and managing stories. Utilize features like media entry, editing, and publishing, alongside effective budget management and workflow optimization. Explore the future of news reporting with advanced integrations for various platforms, ensuring a cohesive multimedia experience.
E N D
CoolStateLA Enterprise System CONVERGED NEWSROOM News Director: Prof. Jon Beaupre CS Adviser: Prof. Russ Abbott
CoolStateLA Enterprise System AGENDA • Ren Almirol: Project Overview • Farrukh Shakil: Asset Manager (Fedora based) • Manoj Katwal: STORI (Fedora based) • Sepideh Nazari: Workflow Manager • Mark Luntzel: Feed Filter • Ren Almirol: Joomla CMS • Prof. Beaupre: Future work • Q & A
Project Overview COOLSTATELA CONVERGED NEWSROOM • University Times Newspaper • CoolStateLA.com News Website • CoolStateLA News Web Radio • CoolStateLA News Webcast
Project Overview COOLSTATELA USERS • Reporter/Producer (RP) • Editor (E) • Assignment Editor (AE) • Senior Editor (SE) • Programmer/News Assistant (PNA) • Advertising Assistant (AA) • News Director (ND)
Project Overview COOLSTATELA TYPICAL USE CASES • Enter Media • Request Edit of Media • Edit Media • Create/Update News Budget • Create/Update Run List • Publish Media • Program Media
Project Overview COOLSTATELA TYPICAL USE CASES • Create Feeds • Propose Story • Confirm Story Proposal • Receive Story Proposal Confirmation • Assign Story • Confirm Assigned Story • Receive Assignment Confirmation
Project Overview COOLSTATELA TYPICAL USE CASES • Create/Update Feeds • Description: A RP or E uses keywords to search feeds for story leads. • Pre-conditions: None. • Post-conditions: System has record of selected feeds for a particular user.
Project Overview COOLSTATELA TYPICAL USE CASES • Propose Story • Description: A producer or editor proposes a story. • Pre-conditions: None. • Post-conditions: A record of the proposed story is stored.
Project Overview COOLSTATELA TYPICAL USE CASES • Confirm Story Proposal • Description: An editor (E, AE, or SE) confirms a story proposal. • Pre-conditions: System has record of proposed story. • Post-conditions: System has confirmatin record of story proposal.
Project Overview COOLSTATELA TYPICAL USE CASES • Receive Story Proposal Confirmation • Description: A RP receives confirmation of a story proposal from an editor. • Pre-conditions: System has confirmation record of story proposal. • Post-conditions: System has receipt of
Project Overview COOLSTATELA TYPICAL USE CASES • Assign Story • Description: An editor assigns a story to a RP. • Pre-conditions: System record of proposed story. • Post-conditions: System has record of story assignment.
Project Overview COOLSTATELA TYPICAL USE CASES • Confirm Assigned Story • Description: A RP confirms an editor’s assigned story. • Pre-conditions: System has record of story assignment. • Post-conditions: System has record of story assignment confirmation by RP.
Project Overview COOLSTATELA TYPICAL USE CASES • Receive Assignment Confirmation • Description: The AE receives assignment confirmation from the RP. • Pre-conditions: System has record of story assignment confirmation by RP. • Post-conditions: System has record of receipt of story assignment confirmation by RP.
Project Overview COOLSTATELA TYPICAL USE CASES • Enter Media • Description: A RP enters media into the system. • Pre-conditions: System has record of story assignment. • Post-conditions: System has record of media.
Project Overview COOLSTATELA TYPICAL USE CASES • Request Edit of Media • Description: The assigned editor requests the RP to edit his story media. • Pre-conditions: System record of media. • Post-conditions: System has record of requested edit of media.
Project Overview COOLSTATELA TYPICAL USE CASES • Edit Media • Description: The RP edits his story media. • Pre-conditions: System has record of requested edit of media. • Post-conditions: System has record of edited media.
Project Overview COOLSTATELA TYPICAL USE CASES • Create/Update News Budget • Description: From list of proposed stories, select stories to be written or deactivated. • Pre-conditions: System has record of proposed stories. • Post-conditions: System has record of stories to be written or deactivated.
Project Overview COOLSTATELA TYPICAL USE CASES • Create/Update Run List • Description: From list of stories to be written, view story status, and select publication destination and date. • Pre-conditions: System has record of active stories. • Post-conditions: System has record of story destinations and dates.
Project Overview COOLSTATELA TYPICAL USE CASES • Publish Media • Description: The editor approves the story to “Publish” status. • Pre-conditions: System has record of entered or edited media. • Post-conditions: System has record of published media.
Project Overview COOLSTATELA TYPICAL USE CASES • Program Media • Description: The PNA and SE work together to program the published story to the appropriate destination (e.g. print, website). • Pre-conditions: System has record of published stories for a particular destination. • Post-conditions: System has record of programmed stories for a particular destination and location.
Project Overview COOLSTATELA ARCHITETURAL COMPONENTS • Asset Manager – Fedora based • Workflow Manager • Workforce Manager – Settle • Newspaper Generator – Adobe InDesign • News Website Generator – Joomla • News Stream Manager and Filter
Asset Manager (Fedora based) • Introduction to Fedora • Similar to database • Stores data and associated metadata • Uses query language iTQL similar to SQL to retrieve data • Advantage to database • Can retrieve and transform data for delivery to different forms of publication (e.g. newspaper, website, cell phone, etc.) using XSL and XSLT
STORI (Fedora based) • Functionality • Current • Inserts, updates, and retrieves story metadata only • Planned • Ingest and update media and associated metadata
Workflow Manager • Who are the users? • How will it be used? • How do these uses map from the Use Cases? • How does the Workflow Manager map from STORI?
Future Work • Integration of architectural components. • Asset Manager • Workflow Manager • STORI – Fedora based • Reporter Alert System • CoolStateLA Radio • CoolStateLA Newscast