Why not just have two logins, one public, and one private? Each has full functionality, except the private one works off a different dataset (that dataset being the data your group enters), and the public one works off a shared dataset. That way, the software is freely available to everyone who might want to use it, but you aren't sharing your data with everyone. Plus! If you can convince other groups to use it, you get the added advantage of being able to see their data, while they can't see yours! Just work your permissions such that the public group sees only public data, whereas the private group sees public *plus* private data. Not that I would condone shady activity in the pursuit of victory, of course, so be sure to make it clear to the public group that anything they enter is visible to all. ;)
Case in point: I work for a remote sensing facility and we use a google maps implementation to assist users in finding data. Anyone can use the interface and search for data. However, not all datasets are publicly searchable. Any user can come in and search for, say, sensing platforms A, B, and C, but only certain users can search for sensing platforms D and C. The only difference is that the public group has checkboxes for A, B, C and the private group has additional checkboxes for D, C. We are not restricting their use of the gmaps api-related software at all, we are simply restricting what is returned by the database. -G --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en -~----------~----~----~----~------~----~------~--~---
