You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"As a content author, I want the system to maintain automatic tags on my content so that I don't have to perform these tasks manually when creating/updating content."
Implement automatic tagging for the system taxonomies defined in the MVP. These tags should be created/updated automatically from the content itself, triggered by the create/update events for courses, blocks, libraries, and library blocks provided by #78
Completion criteria
PR against edx-platform which addresses the behavioral specifications below, and adds the requested management command to manually trigger tag creation.
(Optional) PR against openedx-learning for any logic to extend oel_tagging that may be useful outside of the "content" context.
Automated testing must cover common paths in behavioral specification.
Behavioral specifications
Organization system taxonomy:
When the user creates a new course, block, library, or library block:
a new ObjectTag for that object is created against the Organization Taxonomy.
Use the content's {{usage_key.org}} to locate the matching Organization {{short_name}}, and ensure the ObjectTag is linked to that Organization so that changes to the Organization {{name}} will be reflected when fetching the object tag value.
When the user updates an existing course, block, library, or library block:
if the object already has a Organization ObjectTag, no change is made to that tag. (Organization {{name}}s may change, but once content is created in an org, it becomes part of the identifying usage key, and so cannot be changed.)
if the object does not have an Organization ObjectTag, one is created against the Organization Taxonomy, same logic as with new objects.
When the user deletes a course, block, library, or library block:
any existing Organization ObjectTags for this object are deleted.
When an operator runs the "update tags" management command with a given list of course, block, library, or library block IDs, a new Organization ObjectTag is created if one does not already exist.
Documentation updates & improvements criteria
Ensure that the management command and its options are fully documented.
Note: we may not need these tags at all, as the Organization can be pulled from the object_id usage key, and stored in the search index without the need for tags.
Story
"As a content author, I want the system to maintain automatic tags on my content so that I don't have to perform these tasks manually when creating/updating content."
Full description
Follow up to
Implement automatic tagging for the system taxonomies defined in the MVP. These tags should be created/updated automatically from the content itself, triggered by the create/update events for courses, blocks, libraries, and library blocks provided by #78
Completion criteria
oel_tagging
that may be useful outside of the "content" context.Behavioral specifications
Organization system taxonomy:
Use the content's {{usage_key.org}} to locate the matching Organization {{short_name}}, and ensure the ObjectTag is linked to that Organization so that changes to the Organization {{name}} will be reflected when fetching the object tag value.
Documentation updates & improvements criteria
Relevant repositories
openedx.features.content_tagging
: https://github.com/openedx/edx-platformoel_tagging
: https://github.com/openedx/openedx-learningopenedx-events
: https://github.com/openedx/openedx-eventsThe text was updated successfully, but these errors were encountered: