The settings:
(1) A few options. User can save different versions of the same script for different purposes.
-- "S"-suggest gps and choose to confirm for each document "M"- no suggestion, show all gps for each document in selection
-- Very unlikley to be used: "B" Batch mode, no suggestion, same groups for selection, "A"- just replicate to suggest gps automatically for each document
property gpSelectionMode : "S"
property gpMatchToTags : true -- suggest gps by the tags of group
property gpMatchToName : true --suggets gps by matching words in field "tagor" and conditional to words in "tagand
property numClassifiedToGps : 5
property hourBetweenUpdate : 4
gpSelectionMode: I think “S” semi-auto is the most sensible option. “A” Automatic replication is a bit dangerous, better to test it first and I suggest to enable only gpMatchToTags when using this mode. However, all replications are recorded in log, so user can always undo the actions “one-by-one”.
gpMatchToTags: suggest any group if ALL of its tags are found in the tags of the item. So, I am assuming tag-before-group workflow for this option.
gpMatchToName: suggest any group base on matching the words in the name of the item with the words in the group’s custom meta data fields. The fields are used in common to TaggerV1.1: auto and semi-auto tagging (new option for item's name-only matching). In Tagger, the words are entered in tags. In AutoGroup, words are entered in groups. Punctuation is accepted. For example, user can match “X.XXX” or “Y-YYY” to the name of the items to be grouped.
numClassifiedToGps: the number of DT suggested group to show.
hourBetweenUpdate: same meaning to the Tagger script. When user run the AutoGroup, and if the list of groups and their info haven’t been updated for 4 hours (hourBetweenUpdate:), the script will suggest user to update the list.
The scripts:
(1) Two scripts and one plist file. AutoGroup is the main script, AutoGroup Manual Update is the script for you to manually update the list after you make changes in the tags or wordlist in those groups.
The plist file is essential for maintaining instant response for the script. My scripting is not good enough to know how to optimise the speed on real time processing of the entire database groups’ data.
(2) Tagger and AutoGroup are work-in-progress. I’m still figuring the optimum workflow of tagging and filing. Any suggestion on the workflow and coding are very much welcome!
AutoGroup.zip (522.2 KB)