You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make Public flag not functioning: all contacts for dataresources are displaying on public pages regardless of whether the Make Public is checked or not.
Primary Contact flag not functioning: If a contact is not set as Primary Contact it is still displaying on public page. Description of this flag seems to indicate that only contacts with Primary Contact set should display.
Testing has been completed in both Test and Production environments with the issues described being consistent in both environments.
Summary of Production testing
Note: all page checks completed:
not logged in to ALA
via incognito windows in multiple browsers to eliminate caching issues
Scenario 1
Create new DR with 3 contacts associated. First contact created has Make public set
Rosemary O'Connor-Editor-Public - editor : Editor with Make public set Primary Contactnot set
Rosemary O'Connor-2-Primary-Public - editor : Editor with Make publicset andPrimary Contact` set
Rosemary O'Connor-2-Private - editor : Editor with Make Public**not** set andPrimary Contact` not set
Result: all 3 display on the public page
Based on the descriptions shown when creating these, only Rosemary O'Connor-2-Primary-Public - editor should display on the public page as it is the primary contact. Likely it's ok for both public contacts but a bit confusing if that's not the case and only primary should display.
Rosemary O'Connor-2-Private - editor should not display at all.
Scenario 2
Create new DR with 1 contact associated with Make Public' not set. Checks that issue was not due to first creating an editor contact with the Make Public` set.
Issues
Make Public
flag not functioning: all contacts for dataresources are displaying on public pages regardless of whether theMake Public
is checked or not.Primary Contact
flag not functioning: If a contact is not set as Primary Contact it is still displaying on public page. Description of this flag seems to indicate that only contacts withPrimary Contact
set should display.Testing has been completed in both Test and Production environments with the issues described being consistent in both environments.
Summary of Production testing
Note: all page checks completed:
Scenario 1
Create new DR with 3 contacts associated. First contact created has
Make public
setdr30421
: https://collections.ala.org.au/dataResource/show/dr30241Public Page
: https://collections.ala.org.au/public/show/dr30241Contacts
Rosemary O'Connor-Editor-Public - editor
: Editor withMake public
setPrimary Contact
not setRosemary O'Connor-2-Primary-Public - editor : Editor with
Make publicset and
Primary Contact` setRosemary O'Connor-2-Private - editor
: Editor with Make Public**not** set and
Primary Contact` not setResult: all 3 display on the public page
Rosemary O'Connor-2-Primary-Public - editor
should display on the public page as it is the primary contact. Likely it's ok for both public contacts but a bit confusing if that's not the case and only primary should display.Rosemary O'Connor-2-Private - editor
should not display at all.Scenario 2
Create new DR with 1 contact associated with
Make Public' not set. Checks that issue was not due to first creating an editor contact with the
Make Public` set.dr30422
: https://collections.ala.org.au/dataResource/show/dr30242Public page
: https://collections.ala.org.au/public/show/dr30242Contacts
Rosemary OConnor-Private - Editor
withMake public
not set andPrimary Contact
not setResult: Contact displays on the public page.
The text was updated successfully, but these errors were encountered: