30 lines
1.1 KiB
Org Mode
30 lines
1.1 KiB
Org Mode
|
:PROPERTIES:
|
||
|
|
:ID: ec05ae63-cb3b-486b-af19-4d01e9c10b2f
|
||
|
|
:END:
|
||
|
|
#+title: 2021-12-16
|
||
|
|
|
||
|
|
* Tagging validation issues
|
||
|
|
Met with Ryan M and Chris V to discuss a path forward for dealing with
|
||
|
|
troublesome data submitted to and currently stored in the [[id:7e503917-646f-4275-aab9-3a125b99cbfd][Tagging Service]].
|
||
|
|
** Tags allowing spaces
|
||
|
|
|
||
|
|
** Tags allowing commas
|
||
|
|
https://jira.aweber.io/browse/CCPANEL-11834
|
||
|
|
** Sanitizing / normalizing tags
|
||
|
|
https://jira.aweber.io/browse/CCPANEL-11888
|
||
|
|
|
||
|
|
- Tags are currently normalized to lowercase
|
||
|
|
- Should we normalize spaces?
|
||
|
|
- Should we disallow or remove commas?
|
||
|
|
- Should we validate only new tags?
|
||
|
|
- There is no way for the tagging service to know that a tag is already in use
|
||
|
|
elsewhere
|
||
|
|
- How many tags are in the system that meet our definition of malformed?
|
||
|
|
- Should we start by adding validation?
|
||
|
|
- We could implement a check that only tracks metrics when an added tag fails
|
||
|
|
validation
|
||
|
|
- This can be added to awsubs to see how many subscribers we would fail to
|
||
|
|
add
|
||
|
|
|
||
|
|
Chris will take some additional time to think through the options.
|