Changes

| '''Admin>>Branches>>Queue Actions Page''' <span style="color:red"> After installation of both mods</span><br/>

| '''Admin>>Branches>>Queue Actions Page''' <span style="color:red"> After installation of both mods</span><br/>

This page is similar to the Branch Search page in that it lists all of the branches that match a search, and lets you select or clear checkboxes for each branch. But unlike the Branch Search Page

This page is similar to the Branch Search page in that it lists all of the branches that match a search, and lets you select or clear checkboxes for each branch. But unlike the Branch Search Page

* The tree selection box shows the last Gedcom Import date for each tree.  That date is important to both the program and the user in deciding whether a branch ''needs'' to be rebuilt.

* '''The Search form'''

* The search can focus on the branch name ''or'' description, not both.

*# The tree selection box shows the last Gedcom Import date for each tree.  That date is important to both the program and the user in deciding whether a branch ''needs'' to be rebuilt.

* Three checkboxes affect what is in the result table.

*# The search can focus on the branch name ''or'' description, not both.

*# '''Count labels in each branch''' - As with the branch record counts that [[Admin Branches]] added to the Admin>>Branches>>Search results, by default, the records are not counted, because counting can take too long on a very large database.  Instead, a simply Y or N is displayed by default.

*# Three checkboxes affect what is in the result table.

*# '''Show branch-restricted users''' - This is represented by the very last column of the results.  

*## '''Count labels in each branch''' - As with the branch record counts that [[Admin Branches]] added to the Admin>>Branches>>Search results, by default, the records are not counted, because counting can take too long on a very large database.  Instead, a simply Y or N is displayed by default.

*#* This screen shot was generate from a test database, so most of the branches have no user.

*## '''Show branch-restricted users''' - This is represented by the very last column of the results.  

*#* Still, it is important to realize that not all branches will necessarily have users. Some branches, such as "Contacts", "Ancestors", and perhaps "Hazlet" (which contains ancestors only) are defined simply to identify sets of people in the tree, and are not intended for users.

*##* This screen shot was generate from a test database, so most of the branches have no users. In another environment, displaying this column might make sense only if the search string focused on one or two branches.

*# Focus on dummy branches - A subsequent visualization will illustrate the effect of this checkbox

*##* Still, it is important to realize that not all branches will necessarily have users. Some branches, such as "Contacts", "Ancestors", and perhaps "Hazlet" (which contains ancestors only) are defined simply to identify sets of people in the tree, and are not intended for users.

* The results table (and the buttons just above it) represent a second form, just like in all of the search pages for other database objects.

*## Focus on dummy branches - A subsequent visualization will illustrate the effect of this checkbox

* In the checkbox column, the "Contacts" and "hk" columns do not have checkboxes because they do not have branch rules (Ancestor generations or Descendant generations values)

* '''The results table'''

* The branch 'hk' is a true 'dummy branch', as it is a substring of 'hk-hutch' and 'hk-kuyk' (two closely related families that intermarried). As with most dummy branches

*# In the checkbox column, the "Contacts" and "hk" columns do not have checkboxes because they do not have branch rules (i.e. ancestor or descendant generations values)

** The Actual record count is the union of it constituent branches, which overlap, hence the record counts are not the sum of the constituent branch record counts.

*# The branch 'hk' is a true 'dummy branch', as it is a substring of 'hk-hutch' and 'hk-kuyk' (two closely related families that intermarried). As with most dummy branches

** There are no records in the index, thus the counts are highlighted in red. But, in this case, the difference between the records counts and the index counts are normal, so the highlighting is essentially extraneous.

#** The Actual record count is the union of it constituent branches, which overlap, hence the record counts are not the sum of the constituent branch record counts.

** The branch has never had an action performed on it, since its whole purpose is to reflect the actions of its constiuent branches.

#** There are no records in the index, thus the counts are highlighted in red. But, in this case, the difference between the records counts and the index counts are normal, so the highlighting is essentially extraneous.

#** The branch has never had an action performed on it, since its whole purpose is to reflect the actions of its constiuent branches.

#* In the branch "Durbahn", the last action was "clear", hence the record and index counts are zero. The counts in the People/Families column are non-zero; they reflect the number of records that were cleared.

#* All actions other than "add" are highlighted in brown text.

* In the branch "coffman1", the last action was "clear", hence the record and index counts are zero. The People/Families counts are non-zero; they reflect the number of records that were cleared.

#* The "Clear" action could have been launched from the Branch Edit page, or from this page. There is no way to know.

** All actions other than "add" are highlighted in brown text.

#** The same is true for all "add" actions.

** The "Clear" action could have been launched from the Branch Edit page, or from this page. There is no way to know.

#* The Queued Actions columns is blank because there are no actions in the queue at the moment. See a visualization below.

** The same is true for all "add" actions.

* The Queued Actions column is blank because there are no actions in the queue at the moment. See a visualization below.

#* The "Immediate Action" buttons use Ajax to enqueue add or clear actions for checked buttons.

* The "Immediate Action" buttons use Ajax to enqueue add or clear actions for checked buttons.

#** The results of queued actions are shown in the black box near the bottom of the screen, but are not reflected in the results table until the page is reloaded.  

** The results of queued actions are shown in the black box near the bottom of the screen, but are not reflected in the results table until the page is reloaded.  See a visualization below.

  See a visualization below.

* The Submit buttons were mostly used to test the queuing mechanism, but if an action goes awry, it may be appropriate to use them.

#* The Submit buttons were mostly used to test the queuing mechanism, but if an action goes awry, it may be appropriate to use them.

* This page does not have a way to remove a queued action, though it should. To remove an action from the queue, you must go to the Branch Edit page for the branch whose action you want to remove from the queue.

#* This page does not have a way to remove a queued action, though it should. To remove an action from the queue, you must go to the Branch Edit page for the branch whose action you want to remove from the queue.

* A visualization below shows how the text in the black box is replaced with the results of queued actions.

#* A visualization below shows how the text in the black box is replaced with the results of queued actions.

* Reflecting the use of this page as a testing ground for the queuing mechanism, there are several notes at the bottom of the page.  These notes ''could'' and may be in this Wiki article, as well.

#* Reflecting the use of this page as a testing ground for the queuing mechanism, there are several notes at the bottom of the page.  These notes ''could'' and may be in this Wiki article, as well.

|-

|-

| [[Image:admin_branches_queue-qactions1.jpg]]

| [[Image:admin_branches_queue-qactions1.jpg]]