A content editor chooses the child term of a parent item in its own field. #15
Labels
No labels
A11y
Automated Testing
Contributable
Contributed
Decision
Design
Development
Drutopia
IndieWeb
Infrastructure
Launch Critical
Marketing
Needs documentation
Post-Launch
status
Abandoned
status
Blocked
status
Deploy
status
Doing
status
Done
status
In Review
status
Needs Clarification
status
Test
status
To Do
type
Bug
type
Task
type
User Story
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: geo/geo-coop#15
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Acceptance Criteria
Given that I am a content editor,
when I create an article, blog, page or gleaning,
then I can enter terms for each parent topic,
so that I can easily tag content with the appropriate terms.
Background
We decided that it'd be best for several vocabularies to be combined into the Topics vocabulary.
Work Required
changed the description
marked this issue as related to #5
@mlncn have you confirmed this with Josh? When I talked with him we
decided to keep all those vocabularies as is - separate with the same
names and terms.
I haven't found that widget yet.
@cedewey https://www.drupal.org/project/cshs and https://www.drupal.org/project/shs are the two contenders for D8, can you do a UX review?
A hierarchical vocabulary will be functionally indistinguishable from separate vocabularies, but it will make it possible to reorganize at a future date without another migration.
The only thing missing here is to determine if we are going to use
cshs
orshs
.All the part related with the migration is done :-)
assigned to @cedewey and unassigned @gnuget
changed the description
@gnuget some terms migrated over successfully but not all.
Here is the output on the command line when I ran the migration.
assigned to @gnuget and unassigned @cedewey
@gnuget also, I can just recreate the terms manually if it's going to take awhile to get this fixed in the migration, just let me know. Thanks!
changed the description
CSHS is the only one of the two modules where you can specify a single parent item to associate with a field. For example, the Economic Sectors reference field, having the author only choose child terms of Economic Sectors. So, it's the winner!
mentioned in issue #23
changed title from {-Update taxonomy migrations to merge them into the Topic vocabulary as hierarchical-} to {+A caregiver can see a thumbnail map of the location on programs, events, places, and organizations on their respective pages.+}
changed the description
changed title from A c{-aregiver can see a thumbnail map of the location on programs, events, places, and organizations on their respective pages-}. to A c{+ontent editor chooses the child term of a parent item in its own field+}.
changed the description
changed the description
assigned to @cedewey and unassigned @gnuget
mentioned in commit
4abc28c597
@cedewey OK Client Side Hierarchical Select is installed and enabled, can you take configuring it for these fields?
Thanks!
marked the checklist item Add the Client-side Hierarchical Select module to the project as completed
This is on hold until we can see how Facets will work with the two implementation approaches we're considering.
mentioned in commit
dea557d1a1
Facets work beautifully with the lowest-selected items of a hierarchical topics— set client-side hierarchical select to the lowest, and the editor experience is pretty good too.
Now just to ensure that migration gets in there.
@wolcen can you re-run the site install and migration on test, CI, or anywhere (live if need be)
@gnuget can you re-run locally? There's pretty certain to be more to clean up even if https://gitlab.com/agaric/sites/geo/issues/15#note_205902650 is already addressed.
Closing this and creating a separate migration task.
closed
marked the checklist item Configure the appropriate topic reference fields to use the CSHS-provided widget. as completed
mentioned in issue #48
marked this issue as related to #86
mentioned in issue drutopia/drutopia#279