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
On the WhatDoTheyKnow Community & Activism call last night we discussed wanting to have the ability to remove a group of authorities from the internal search index.
We could do this one of two ways.
By adding a noindex special tag
By adding Prominencable with a backpage option
Using a noindex tag would likely be marginally quicker to implement – basically:
Adding Prominencable might be a little extra work, but have some additional benefits.
It would be more consistent with other similar record types and better integrate with the “eye” icon around the admin interface, and we could later add the hidden state which would allow us to draft forthcoming authorities (#7298) without them being visible.
Another benefit, especially for the group of authorities we discussed, is that backpage also prevents external indexing. Looks like we have an easy mechanism to apply this via ProminenceHeaders.
The text was updated successfully, but these errors were encountered:
On the WhatDoTheyKnow Community & Activism call last night we discussed wanting to have the ability to remove a group of authorities from the internal search index.
We could do this one of two ways.
noindex
special tagProminencable
with abackpage
optionUsing a
noindex
tag would likely be marginally quicker to implement – basically:Adding
Prominencable
might be a little extra work, but have some additional benefits.It would be more consistent with other similar record types and better integrate with the “eye” icon around the admin interface, and we could later add the
hidden
state which would allow us to draft forthcoming authorities (#7298) without them being visible.Another benefit, especially for the group of authorities we discussed, is that
backpage
also prevents external indexing. Looks like we have an easy mechanism to apply this viaProminenceHeaders
.The text was updated successfully, but these errors were encountered: