Folder & Automatic Grouping for Patrols
(Original title: Folder organization for patrols)
Could we add the ability to create folders in the Patrol Perspective, so that you could place patrols into user-defined folders (e.g., by patrol team name, year, etc.)?
Could we add the ability to create folders in the Patrol Perspective, so that you could place patrols into user-defined folders (e.g., by patrol team name, year, etc.)?
Leave a comment
on 2016-10-25 04:33 *
By rsapickles
Absolutely. have you seen how this is handled in Garmin Basecamp? With several SE Asian sites dealing with small teams in huge landscapes we use Basecamp to manage our patrol GPX track and waypoint data separate to SMART as this is easier for managing data to go back on to the GPS units. I would like to see SMART have a similar degree of useability as the folder and list system of Basecamp, where you create a 'playlist' of tracks and waypoints. Attached guide shows how we use Basecamp
file:aKHX-SMO0r5Rdcdmr6CpXy
file:aKHX-SMO0r5Rdcdmr6CpXy
RRI Discussion:
There are a variety of options we could implement here:
Automatic Grouping
This would create an option where users could view the patrols grouped by any one of a collection of fixed options. I’d suggest something like: “View By: Month & Year, Year Only, Station, Team, Mandate.
Users could easily switch between the various group by options.
This has the benefit of the patrols being automatically classified without the user having to select a folder or tags.
This is the easiest to implement and the least flexible.
Folders
This is what is asked for in the ticket. Users create folders and drag and drop patrols into the folder. Patrols can only belong in a single folder. Folders can have sub folders (similar to queries).
Each time a patrol is added to the system users will have to pick a folder to place it into. This would be true for manual patrol entry and Cybertracker data importing.
Tags / Labels
Similar to GMail Labels & Assembla tickets tags one or more tags could be added to a patrol. You could then easily filter patrols on these tags or group by the tags (one folder per tag).
GMail allows users to nest “labels” so users could still get a hierarchical folder structure if desired.
As with folders, users would have to apply tags to patrols when they are created or imported.
This is the more difficult to implement but also most flexible.
There are a variety of options we could implement here:
Automatic Grouping
This would create an option where users could view the patrols grouped by any one of a collection of fixed options. I’d suggest something like: “View By: Month & Year, Year Only, Station, Team, Mandate.
Users could easily switch between the various group by options.
This has the benefit of the patrols being automatically classified without the user having to select a folder or tags.
This is the easiest to implement and the least flexible.
Folders
This is what is asked for in the ticket. Users create folders and drag and drop patrols into the folder. Patrols can only belong in a single folder. Folders can have sub folders (similar to queries).
Each time a patrol is added to the system users will have to pick a folder to place it into. This would be true for manual patrol entry and Cybertracker data importing.
Tags / Labels
Similar to GMail Labels & Assembla tickets tags one or more tags could be added to a patrol. You could then easily filter patrols on these tags or group by the tags (one folder per tag).
GMail allows users to nest “labels” so users could still get a hierarchical folder structure if desired.
As with folders, users would have to apply tags to patrols when they are created or imported.
This is the more difficult to implement but also most flexible.
Automatic Grouping: yes
Could we also have the folder option, for example to accommodate the case where you have patrols where the data are still waiting for checking/editing/review, vs patrols that have been processed already.
I don't think we need to go as far as tags if we have the first two options.
Could we also have the folder option, for example to accommodate the case where you have patrols where the data are still waiting for checking/editing/review, vs patrols that have been processed already.
I don't think we need to go as far as tags if we have the first two options.
Automatic Grouping
This would create an option where users could view the patrols grouped by any one of a collection of fixed options.
Group options should consist of:
Folders
When users select the folder group by option they can:
Patrols can only belong in a single folder.
Folders can have sub folders.
When creating a new patrol (UI or CT) if folders are defined in the system then give the user an option of selecting the folder to add the patrol to; otherwise do not display this option.
Patrols within the group are ordered by the existing order by option in the filters dialog (Patrol ID, start date or end date). We could potentially add another button the toolbar to make changing the sorting option easier but I'm not sure this is necessary.
This would create an option where users could view the patrols grouped by any one of a collection of fixed options.
Group options should consist of:
- Folders
- Stations
- Team
- Patrol Type
- Mandate
- Year
- Month & Year
Folders
When users select the folder group by option they can:
- create new folders/delete folders/ rename folders
- drag and drop patrols into the folder
Patrols can only belong in a single folder.
Folders can have sub folders.
When creating a new patrol (UI or CT) if folders are defined in the system then give the user an option of selecting the folder to add the patrol to; otherwise do not display this option.
Patrols within the group are ordered by the existing order by option in the filters dialog (Patrol ID, start date or end date). We could potentially add another button the toolbar to make changing the sorting option easier but I'm not sure this is necessary.
In the release of 6.999.1, I encountered an error (see log extract below) and have a couple minor UI enhances that would make the folder options easier on the user.
UI Features
- when a folder is created there is no way to rename it. It comes with the default name of <None>
- it appears that many patrols can be selected for dragging into a custom folder but only one of the selected patrols actually is inserted into the new folder.
Error
UpdatePatrolList.txt
UI Features
- when a folder is created there is no way to rename it. It comes with the default name of <None>
- it appears that many patrols can be selected for dragging into a custom folder but only one of the selected patrols actually is inserted into the new folder.
Error
UpdatePatrolList.txt