Slightly old, but a friend of mine started this : https://fedorahosted.org/shomyu/

CC: (none) => misc

This looks promising - could probably be automated.
http://www.aardvarkmap.net/

CC: (none) => zen25000

I wondered about having this info (Country/City) into our LDAP? or better have it separate?

Country/city can already be done with localityName and countryName, but no schema seems to use it so far.

Having in ldap would be convenient as this permit us to manage from identity. But I think a country/city is maybe not the most convenient to store information about location as we may have hard time to convert this to spatial coordinates. And there is no ( AFAIK ) schema to store coordinate.

Storing this in postgres would be nicer from a dev point of view, as postgis is a quite powerful extension to postgres. Spatialite could be used for sqlite too.

Using some nosql db would also be a option, but I do not know what exist for that.

There is "geocouch" and "mapquery" (at FosGiss I listened to a presentation by geocoach's main developer), perhaps we could build a simple application arround this.
But my colleagues from work whose main work is in the webgis development meant it couldn't replace postgres/postgis.

I'll have a look into it.

CC: (none) => oliver.bgr

Another solution would be to add a field for Country in mageia phpbb3 forum like kde forum http://forum.kde.org/index.php
In the KDE forum there are the options "Country" and "Location"
In the location i putted "France" as i live in France and i want to meet people from France but in the "Country" i putted Greece because i am Greek and i want to meet people from Greece too, as the community that i am active is the Greek

(In reply to comment #4)
> Country/city can already be done with localityName and countryName, but no
> schema seems to use it so far.

Is this complex to add

> Having in ldap would be convenient as this permit us to manage from identity.
> But I think a country/city is maybe not the most convenient to store
> information about location as we may have hard time to convert this to spatial
> coordinates. And there is no ( AFAIK ) schema to store coordinate.

We could centralize the Country/City info in LDAP and have a separate db to map this to coordinates (there are geocoding services that we could cache the result from - it's only about cities, so that's not hugely extensive data to store).

Otherwise, yes, having a dedicated small db for this would make it. Do we need more than these two relationships?
 * user lives in place (or even places but that makes it out of LDAP I think, let's keep it simple)
 * place has coordinates

> Storing this in postgres would be nicer from a dev point of view, as postgis is
> a quite powerful extension to postgres. Spatialite could be used for sqlite
> too.
> 
> Using some nosql db would also be a option, but I do not know what exist for
> that.

I don't have specific knowledge about the best backend for this. So far, I can just envision the end-result (interactive map + find my neighbours query by group) and the user info filling.

(In reply to comment #6)
> Another solution would be to add a field for Country in mageia phpbb3 forum

I would keep this out of the forum:
 * doesn't require a user to sign in the forum to record this info;
 * so we can have simpler, dedicated/optimized queries for extraction.

A small separate app can make it.

(In reply to comment #7)
> (In reply to comment #4)
> > Country/city can already be done with localityName and countryName, but no
> > schema seems to use it so far.
> 
> Is this complex to add

into our setup?

See a similar initiative: https://mozillians.org/

> Country/city can already be done with localityName and countryName, but no
> schema seems to use it so far.

'l' is an alias for 'localityName', and organisationalPerson->inetOrgPerson has it. They also have 'st' for 'state' and 'postalCode'

It would be relatively easy to add support for additional attributes to hold locality data (e.g. adding contryName or 'c' is relatively trivial).

To do it properly, we should request an enterprise number from IANA so we can have viable schema definitions (that can be published).

The biggest issue is how to store coordinates, e.g. as as plain string, or as attributes dedicated for longitude or latitude (which impacts whether you can easily store multiple values).

> Otherwise, yes, having a dedicated small db for this would make it. Do we need
> more than these two relationships?
>  * user lives in place (or even places but that makes it out of LDAP I think,
let's keep it simple)

Easy if we don't consider coordinates, we use a multi-valued attribute.

'l' or 'localityName' is multi-valued.

[bgmilne@tiger bgmilne]$ ldapsearch -LLL uid=bgmilne l 2>/dev/null
dn: uid=bgmilne,ou=People,dc=ranger,dc=dnsalias,dc=com
l: Cullinan
l: Centurion
l: Lagos
l: Cape Town

> * place has coordinates

If you want to store one, no problem. Many options open, format being the biggest issue to worry about (decimal or not).

If you want multiple ones, easy if latitude and longitude stored together as a single string, or using any other coding that results in unique strings.

If you want to associate to localityName's, more difficult.

CC: (none) => bgmilne

(In reply to comment #10)
> 'l' is an alias for 'localityName', and organisationalPerson->inetOrgPerson has
> it. They also have 'st' for 'state' and 'postalCode'
> 
> It would be relatively easy to add support for additional attributes to hold
> locality data (e.g. adding contryName or 'c' is relatively trivial).

Cool.

> To do it properly, we should request an enterprise number from IANA so we can
> have viable schema definitions (that can be published).

Yep, I can do that. Go for it?

> The biggest issue is how to store coordinates, e.g. as as plain string, or as
> attributes dedicated for longitude or latitude (which impacts whether you can
> easily store multiple values).

I am not sure we should store coordinates in LDAP:
 - we would ask only for country and locality name to people, for their account,
 - a separate app will use that as a reference and make the geocoding (for mapping, matching, etc.).

> > Otherwise, yes, having a dedicated small db for this would make it. Do we need
> > more than these two relationships?
> >  * user lives in place (or even places but that makes it out of LDAP I think,
> let's keep it simple)
> 
> Easy if we don't consider coordinates, we use a multi-valued attribute.
> 
> 'l' or 'localityName' is multi-valued.

Excellent.

> > To do it properly, we should request an enterprise number from IANA so we can
> > have viable schema definitions (that can be published).
> 
> Yep, I can do that. Go for it?

Please.

We will need to discuss how we maintain the OID space, but we could just have a project in svn to maintain the schema.

Request sent to IANA.

"The Private Enterprise Number 38772 has been assigned to your organization."

bump

CC: (none) => alien

btw: didn't we have some static map manually made for some communcations? i remember someone asking me for my location for that...

It still requires an update in the LDAP schema; I have a skeleton app (https://github.com/rdalverny/victor/) getting info out of the LDAP into user/group pages + a map, but it still needs the LDAP to provide the info + some more caching works.

No static map either for the time being.

did anyone make the schema attributes (quite easy) and add them to the openldap? is there a subrequest that should be blocking this one? is someone assigned to do this?

(In reply to AL13N from comment #18)
> did anyone make the schema attributes (quite easy) and add them to the
> openldap? is there a subrequest that should be blocking this one? is someone
> assigned to do this?

Sorry for the late reply (21 months later)

As you can see, this bug was assigned to obgr_seneca.

When I go to identity.mageia.org, and look at the attributes for me, there is a "PreferredLanguage" field, but nothing for country or city.

The country code of a mobile phone number could be used to determine in which country someone lives, if everyone has that field. Do you have that "mobile" field, too? (See "Add an attribute" at the bottom of the list.)

Does anyone know whether that mobile phone number would show up anywhere, if one is added?

CC: (none) => marja11

(In reply to Marja van Waes from comment #19)

> 
> The country code of a mobile phone number could be used to determine in
> which country someone lives, if everyone has that field.

I just put nothing but my country code (+31) in the "mobile" field. That was accepted.

Reassigning to sysadmin team, lowering Severity to enhancement.
Reverting Status to NEW.

Keywords: Atelier => (none)
Assignee: oliver.bgr => sysadmin-bugs
Status: ASSIGNED => NEW
Severity: normal => enhancement