From 6329b624c5423cd218743b83dfae9d44f58e0394 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 6 Sep 2018 19:50:25 +0000 Subject: [PATCH] --- devdocs/specs/core-tags.txt | 16 +++++++++++++--- devdocs/todo.txt | 7 +++---- 2 files changed, 16 insertions(+), 7 deletions(-) diff --git a/devdocs/specs/core-tags.txt b/devdocs/specs/core-tags.txt index 78dd3af1..a089bdab 100644 --- a/devdocs/specs/core-tags.txt +++ b/devdocs/specs/core-tags.txt @@ -2,7 +2,7 @@ Main case is 3373 https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3373 -TODO: TAG-GROUP - bag of tags +TAG-GROUP - bag of tags Modify the below and coded and tests and tables to now have feature for tag groups They will be in their own table with a dictionary table of tag ids and tag group id's to link They are used for read purposes, you never tag an item with a tag group, only query by group. @@ -10,6 +10,7 @@ TODO: TAG-GROUP - bag of tags If a tag is deleted it must be removed from any tag groups and if there are no other items in that tag group then the tag group must be deleted as well?? - Or maybe is just an empty group with a warning symbol in ui Tag groups will become a major way to save filters for things because a lot of filtering will be by tags so this should be a solid feature. + - RETRIEVAL / PICKLISTS: need to modify the tag picklist to optionally return TAGGROUP names as well as identify they are group so UI can feature differently FORMAT =-=-=- @@ -24,17 +25,26 @@ tags ... SCHEMA =-=-=- -Two tables: +4 tables: TAGS - name text not null lowercase only - id bigserial - OwnerId - - Created + TAGMAP - ObjectId - ObjectType - TagId + +TAGGROUP + - name text not null lowercase only + - id bigserial + - OwnerId + +TAGGROUPMAP + - TagGroupId + - TagId INDEXES - Initial index is on the name of the tag as that will be searched for?? diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 5e5b6bd9..434863cd 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -29,15 +29,14 @@ IMMEDIATE ITEMS: ================ - - USER OPTIONS OBJECT - - UserOptions object and routes will be used for user configurable settings, some of it initial shell (timezone, email etc), not core User stuff to avoid any rights issues or confusion or bypasses - - Make user options now even if it only has one setting, I will need it ongoing all the time for a ton of shit. - - Tag groups (modify tags already coded) + - Retag: code to tag an item should take into account if it's already tagged and not make a new record, just return existing - Localized text - ** DEVISE a system to ensure no unused keys are brought forward to raven - Search and search text indexing + - Add to widget tests - Auto visible id number assigning code + - Give widgets a visible ID number scheme and add to tests