Mediafly DocumentationBest Practices ArticlesImplementing New Content Structure

Implementing New Content Structure

This article outlines the best practices if you have a current library of content setup in Airship that requires updates, whether it be adding a new product line or an entirely new content set, with limited impact to end users. Using our best practices, you can begin working on your new content structure in Airship and choose the date and time you want the new content to be revealed to end users in the Apps and Viewer while simultaneously archiving outdated content.

We recommend using a combination of the Release and Archive features to manage the implementation of a new content structure. Supporting article related to managing Time-Sensitive Content using the Release and Archive features.

Recommended Steps

  1. Draft out and finalize new content structure on paper
    .
  2. Set date that transition will occur
    .
  3. Using main admin Airship account, set archive date in the metadata for content that will no longer be used in new structure
    .
  4. Using main admin Airship account, begin creating new folders and adding content
    .
    • Ensuring to set release date in metadata for newly added content.
    • Add groups and permissions to new folders/content
    .
    • Tip: Bulk edit feature can be utilized to set archive or pre-release for multiple items.

Recommended to test release and archive date feature with a small group of users to ensure it fits the needs of the implementation project.

Viewing New Content Structure Prior to Launch

Create a test account in Airship to use for transition process. The objective of the test account is to have a way to cleanly see what the new structure will look like without the distraction of the existing structure. \L

  • In Airship: Test account should have limited Manage Media privileges. Privileges should only be given to the content/folders in the new structure. \L
  • In App: To view what the new structure will look like in the apps, the test account can have limited View Media + Pre Release privilege. They are then given user access to only the new structure and Pre Release enables them to view despite Release Date. \L

Additional Notes

  • Although it is not a feature to add an archive or release date at the folder level, if ALL the content inside of the folder has an archive/release date of the same day, it will become visible/invisible to the end user\L
    • Example: If a folder has content that is set release on 6/5/15, end users will not be able to see the folder or content until 6/5/15. Similarly, if a folder has content that that is set archive on 6/5/15, end users will no longer see the folder or content on 6/5\L/15.
  • Users who have manage all content access in Airship will be able to see new folders being added to Airship. We recommend informing these users about the transition. \L
  • Pre-Release permission on the user/group level can be used in conjunction to give certain people access to view newly added content in the app before it is released to all users\L More Information

Example of main admin Airship account

Example of main admin Airship account

Using your main admin Airship account, you can see the current content (red) and content set with archive and release dates (blue)

Example of test admin Airship account

Example of test admin Airship account

Using your test admin Airship account, you can use limited manage media permissions on Release content to view only the new content structure

Example of end user view: Pre-Launch

Example of end user view: Pre-Launch

When content is set with release date, end users will not see this content in their app until the release date. Similarly, the archive folder will no longer show for end users after the archive date.

Example of user view: Post-Launch

Example of user view: Post-Launch

Release content is now in view and Archive content is no longer visible

0 Comments

Add your comment

E-Mail me when someone replies to this comment