Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Page Properties

Status

Status
colourRed
titlenot visible to public
Status
colourYellow
titleready for review
still need to make the diagram

Type

Explanation/Reference

Reader

Clients / CSMs

Reader goal

Decide how to pull and sort content for a module, most likely coming from one of these mindsets…

  • They have a specific idea (use case) in mind – “Can I do this?” If they are tech/design savvy they might look at this on their own. Otherwise, they might ask a CSM, “can I do this?” and the CSM would look at this doc to find the answer.

  • Or they/CSM have a template or prebuilt module that they want to adjust. “I want to change this default. What are all my options?”

They do NOT want to think about how it all works on the back end. They are focused on use case.

Learning goal: Understand all parts of how content is pulled and sorted. Be able to fill in the “formula” with their choices and hand it to the CSM/Config team

Contributors

Nelly, Scrilla

JUNO version

Reviewers (check the box when you’re done!)

  •  Scrilla
  •  Travis
  •  Some CSMs
  •  Leon (just the recommended tags section)

Review deadline

Notes for reviewers

Let me know if anything comes to mind that’d make something easier to understand. (smile) Thank you all. This one’s a beast! (smile)

  • Scrilla, the red section at the bottom is particularly for you.

  • Leon, Scrilla and I would like some assistance making sure I got the add_users_tag_types and require_some_preferred_tags_of_type right. It’s the Personalized recommendations section.


...

The goal of this module is:

Pull these content type(s): This step is required. The rest are optional.

Then narrow it down…

  • Only with this session status:

  • Only with these tag(s):

  • Make personalized recommendations based on access level: Specify Strict or Flexible

  • Makepersonalized recommendations based on these profile tag types: Name tag types and specify Strict or Flexible

Then sort it all by:

...

Anchor
pull
pull
1. Pull content types (required)

...

Choose one way to sort…

Definition

(tick) Release date (most recent first or last)

Release is when the content becomes viewable. For example, a piece of library content might not be released until a specific date. A session might be released well before it’s start time.

(tick) Start date (most recent first or last)

Start is when a session begins. This is only for sessions.

(tick) Alphabetical by title

Note that speakers are sorted by the first character in their name.

(tick) Numerical by title (ascending or descending)

Use this if the first character in the title is a number. For example, 1 Library and 2 Library. Note this doesn’t work if the first character is a letter. For example, Session 1 and Session 2 will not sort numerically.

(tick) Random

Changes each time you reload the page.

(tick) Popularity

Tag score then date.

Warning

Unsure if these have a use case for modules/what they are

  • 1 = sort num responses descending 

  • 5 = sort children descending 

  • 6 = sort children ascending 

  • 12 = sort day and month ascending 

  • 13 = sort rotate every four hours 

  • 14 = sort rotate every hour

  • 16 = sort string option1 

  • 17 = sort string option2 

  • 18 = sort string option3 

  • 19 = sort match against score 

  • 21 = sort child ascending2 

  • 22 = sort content descending2 

  • 100 = sort pinned tag 

  • 101 = sort bucket tag ascending 

  • 102 = sort getty special 

  • 103 = sort tag order 

Pretty sure these aren’t for modules…

  • 10 = sort rank descending 

  • 11 = sort rank ascending 

  • 9 = sort action completed 

  • 23 = sort most completed action 

  • 24 = sort least completed action 

...