Shareable Content Sub-site

1 x Sub-site created to centralise sharable content types (news, events etc)
Purely infrastructural - content editors will not need to access / view / navigate the sub site
No URL required to be applied to the site
Authoring will be conducted on Faculty or School sites
Permissions applied for editing rights to appropriate user groups
Allows centralised listing of items

Edit Plus Customisation

Create 2 x Custom Edit Plus Plugins

Extra Edit Plus Tab: Tagging (possibly) & Request for Listing on other sites
- Viewable if in correct user group
- Interface to select terms to tag with (or this could just be done on the metadata screen)
- Interface tick list of sites to publish on
- Provides button to apply
- Shows status of requests once made
- Ability to cancel request?
Extra Edit Plus View: Manage Pending Requests
- Icon in the toolbar links to Manage Pending Listing Requests page / modal
- Lists pending requests for publishing
- Links to items for previewing
- Controls to approve or decline
- Notifies requester of decision

Event & News Assets

Metadata: 2 hidden (from Metadata Tab) multiple text metadata fields containing an array of JSON objects:

First field tracks publishing requests (1 per site that can be requested).
If a request already exists for a particular site, the interface shows the status of the request - 'Pending', 'Declined' or 'Approved' - instead of tick field and a 'Cancel' link (to cancel the request)
Each request object needs to capture an ID, date and requester details incase they are made at separate times by separate people. i.e. someone edits the event at a later point and requests publishing on more sites than originally requested.
JSON objects contain:
- Request ID (ISO 8601 convert the date and time at that moment, which will create a unique string)
  - var d = new Date(); var n = d.toISOString(); the results of n will be - 2016-09-12T20:49:26.101Z
- Site Name
- Site ID
- Admin Group ID
- Request Status
- Date of Request
- ID of Requester
- Name of Requester
Second field tracks approved sites
- Request ID
- Site Name
- Site ID
- Date of Approval
- ID of Approver
- Name of Approver

First field drives the interface, second field is for searching / listing i.e. only sites that are approved will have a corresponding JSON object in the second field. On decline, only the first field object needs updated. On approval, first field needs update and second field needs a corresponding approval object created - using the same request ID as the first to link them.

Triggers

One trigger configured to accept post requests (on asset accessed) that send 'Request for Listing' notification emails
One trigger configured to accept post requests (on asset accessed) that send 'Request Decision' notification emails
One trigger configured to create a link to the event being created under the central shareable content site

Publishing Listings

Configured to search 2nd metadata field

Publishing Widgets

Selectable template type, i.e. News Listing, Events Listing etc
Interface to select relevant tags to use to find relevant items
Formulates query to pass to Matrix Search or GSA

Browser not supported