Ideas

Add a "TaggedItems" Property to the Content Channel Item Model

Note You are not authorized to edit this feature.

Add a "TaggedItems" Property to the Content Channel Item Model

CMS

Currently, getting a list of tags associated with a content channel item (to my knowledge) requires either an entity command or SQL. Let's make this easier to access by adding a TaggedItems property on the ContentChannelItem model that would return a lava object with the tags associated with the content item.

{% assign tags = Item.TaggedItems %}
{{ tags | ToJSON }}
[
  {
    "Id": 170,
    "Guid": "76c7e200-f310-4a38-8f10-a6596f8b9ff9",
    "Name": "healing",
    "Description": ,
    "IconCSSClass": "",
    "CategoryId": 979,
    "AttributeValues": [
      {
        ...
      }
    ]
  },
  {
    "Id": 173,
    "Guid": "c0c8c83c-3e0c-4223-a62b-339a17511988",
    "Name": "marriage",
    "Description": ,
    "IconCSSClass": "",
    "CategoryId": 979,
    "AttributeValues": [
      {
        ...
      }
    ]
  }
]

I think it would be helpful to include the following tag data in the object that is returned.

  • Id
  • Guid
  • Name
  • Description
  • Icon CSS Class
  • Category
  • Attribute Values

Initially, I think this could be limited to Organizational scoped tags, but if not, we would want to include the OwnerPersonAliasId so that it could be filtered on. I also would not expect inactive tags to be returned.

This would be specifically helpful on content channel items, but since tags can technically be applied to any entity, this could be something that is added to all models.

Photo of Brian KalwatSubmitted by Brian Kalwat, NewSpring Church  ·   ·  CMS
Login to add a comment...

Submission Success Tips

Cultivate your ideas for maximum impact with these helpful submission tips that will increase the chances of your brilliant concepts becoming reality.

  • Clear Title: Craft a straightforward and descriptive title that instantly conveys the essence of your idea.
  • Concise Description: Provide an idea description that is succinct, ensuring it effectively communicates the concept without unnecessary verbosity.
  • Provide Additional Details: With a concise description complete, now provide any other details that are needed to better understand the requirements.
  • Thorough Ministry Need Review: Provide a comprehensive overview of the ministry need your idea addresses, emphasizing its significance.
  • Cover the WHY: Clearly articulate the rationale behind your idea, explaining why it's essential and how it aligns with the organization's goals and mission. Oftentimes a clear "why" sheds light into other possible options.