Re: [Arches] Best practices for place data not meant for publication

2015-12-09 Thread Lucy FJ
Hi Adam and Angela,

We would be very interested in knowing how to do this too. In fact, I 
thought this had already been planned as a function of Arches? 

Thank you very much Angela, for raising the issue and thank you for Adam, 
in advance, for your suggestions.
 

On Wednesday, December 9, 2015 at 3:27:00 AM UTC+2, Adam Lodge wrote:
>
> Angela, 
>
> Unfortunately, your read on this is correct.  There is currently no 
> out-of-the-box way to satisfy this use case built into the Arches 
> framework.  
>
> Depending on the specifics of what you want, however, there are a few ways 
> to build application-specific customizations might meet the need.  I could 
> suggest a one or two approaches if that would be valuable to you.
>
> Best,
> Adam
>
> -- 
> Adam Lodge
> Geospatial Systems Consultant
> Farallon Geographics
>
> On Tuesday, December 8, 2015 at 8:11 AM, 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 arches...@googlegroups.com . To 
> unsubscribe, send email to archesprojec...@googlegroups.com . 
> 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 archesprojec...@googlegroups.com .
> For more options, visit https://groups.google.com/d/optout.
>
>
>

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [Arches] Best practices for place data not meant for publication

2015-12-08 Thread Adam Lodge
Angela, 

Unfortunately, your read on this is correct.  There is currently no 
out-of-the-box way to satisfy this use case built into the Arches framework.  

Depending on the specifics of what you want, however, there are a few ways to 
build application-specific customizations might meet the need.  I could suggest 
a one or two approaches if that would be valuable to you. 

Best,
Adam

-- 
Adam Lodge
Geospatial Systems Consultant
Farallon Geographics


On Tuesday, December 8, 2015 at 8:11 AM, 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 archesproject@googlegroups.com 
> (mailto:archesproject@googlegroups.com). To unsubscribe, send email to 
> archesproject+unsubscr...@googlegroups.com 
> (mailto:archesproject+unsubscr...@googlegroups.com). 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 archesproject+unsubscr...@googlegroups.com 
> (mailto:archesproject+unsubscr...@googlegroups.com).
> For more options, visit https://groups.google.com/d/optout.

-- 
-- To post, send email to archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[Arches] Best practices for place data not meant for publication

2015-12-08 Thread Angela Labrador
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 archesproject@googlegroups.com. To unsubscribe, send 
email to archesproject+unsubscr...@googlegroups.com. 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 archesproject+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.