I would second this (+1) as a valuable additional feature for Arches. While personally I'm very much on the Open Information side, there are sites which need to be managed (and receorded in systems such as Arches) without making precise locational information availailable to all. Ed
On Tuesday, December 8, 2015 at 4:11:40 PM UTC, Angela Labrador wrote: > Hello all, > > Apologies if this has already been addressed: > > I'm dealing with a use case wherein a particular heritage site's location > is "Not for publication" but still needs to be tracked within Arches by > authenticated users. The ACL grants permissions per node, and I have not > found a flag that allows for per instance override (e.g. by default all > locations are available to anonymous users, but if field_x=true or > address_type="private" then the place data are only available to > authenticated users). > > Since this is a common issue with archaeological sites and certain > Indigenous and sacred sites, I'm wondering how others have dealt with this > or if I'm missing something obvious. > > Many thanks, > Angela > > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
