Skip to content
Heather Bryant edited this page Apr 11, 2018 · 3 revisions

An Organization is a company or news organization on the platform.

  • Organizations are created by a user. That user is the organization owner. Multiple users can be an owner. (Redundancy for turnover)
  • Organizations have users. Users are added by the organization owners.
  • Organizations "own" the content created by users affiliated with that organization.
  • Organizations can create networks "owned" by that organization and invite other organizations to join. To do so, an admin of the organization that owns the network invites the admin of another organization using the admin's email. (This is the basic level of this functionality and relies on previous interaction between admin's in order to know the email to send the invitation to. This also prevents organizations from getting spammed by network invites.)
  • Organizations can be in as many networks as they want to be in. (In the long run, this functionality will necessitate some form of filtering and/or "retiring/archiving" of networks that have reached an end-date.)
  • Organizations that join a network are partners of the other organizations in that network. Team members from partner organizations become available options both in communications and in selecting and assigning tasks in content that has been marked as "collaborative" with specific organizations in a network or the network as a whole.
  • Organizations can collaborate with partner organizations or entire networks. Projects, series and stories can be marked as Collaborative and select the partners involved. A collaborative item is accessible and editable by the team members of the organizations involved. (Ex. Criterion News creates an Coastal News Network and adds the Arctic Times and Wolf Media to that network. Criterion News creates a story, "Whale populations reach record numbers," and sets it as collaborative. They can then select either the Arctic Times or Wolf Media or the Coastal News Network as collaborating partners on "Whale populations reach record numbers." The editor of that story can now assign team members from the collaborating partner(s) to the story.)
  • Organizations can also share with partner organizations or entire networks. Sharing is intended as a distribution mechanism and is available on stories. A shared story appears in the network content feed. An Organization can see all the stories available to them and collect that story by making a copy. The story then appears in the organization's content dashboard and is available to team members. CopyDetails are recorded and include all the relevant fields. (More details on how copying works in the content model documentation)

Organization Use Cases

Organization: Internal collaboration

Example: Criterion News is an organization that has a newsroom of 16 people working across digital, video, audio and print platforms. Criterion uses Facet to plan stories across teams and platforms and manage daily editorial workflow.

Organization: External collaboration

Example: Wolf Media is a newsroom of 8 people that belongs to a regional collaborative network. Wolf Media regularly shares content and picks up content from partners. Occasionally Wolf Media contributes to a collaborative project of series with partner organizations.

Organization: Relationship management of independent users (Not part of Base Functionality. Must opt-in.)

Example: Arctic Times is a small organization of 2 people. Content is largely produced by a network of regular freelancers. Arctic Times uses Facet to solicit and accept pitches from regular contributors, manage the editorial process with them and to discover new contributors.

Considerations

This functionality can easily be over complicated and will be built out as further features and needs are identified. The initial version of the platform will focus on three main utilities for Organizations:

  • internal workflow and collaboration
  • collaboration with partners inside of networks
  • managing the relationship between organizations and independent users.

Fields

Organization

name

  • Should allow for diacritic marks, spaces and hyphenation.

owner

  • User that created the organization.

description

  • Short profile description of the organization.

logo

  • Image representative of the organization to attach to all public profiles.

location

  • Primary location of the organization.

creation_date

  • When the organization was created on the platform.

website

  • The organization's website. (This may have to be a separate table as many organizations now have multiple domains to keep track of.)

notes

  • The notes associated with the Organization and accessible to all Organization users.

Data Model

Actors & Associations

Content

Assets

  • ImageAsset
  • DocumentAsset
  • AudioAsset
  • VideoAsset
  • SimpleImage
  • SimpleDocument
  • SimpleAudio
  • SimpleVideo

Notes

  • Notes

Tasks

  • Tasks

Events

  • Events

Communication

  • Comment
  • Discussion

CopyRecords

  • StoryCopyRecord
  • FacetCopyRecord
  • ImageAssetCopyRecord
  • PrintAssetCopyRecord
  • AudioAssetCopyRecord
  • VideoAssetCopyRecord

Clone this wiki locally