[Tagging] How one should tag different sections of library?

Mateusz Konieczny matkoniecz at gmail.com
Tue Dec 2 06:28:47 UTC 2014


"I would ask if any section of that library is usable as a library on it's
own."

Without registration it is impossible to use any, there is a single place
for registration. Books/media must be returned to the same section where it
was borrowed. In this case everything is in a single building (building
hosts only library and some small related business like newsagent's shop).

On other hand each library as collection of books is usable on its own and
borrowing limits (3 books or something like that) are separate.


2014-12-02 0:19 GMT+01:00 Peter Wendorff <wendorff at uni-paderborn.de>:

> I would ask if any section of that library is usable as a library on
> it's own.
>
> Let's take the local city library here, which has several sections at
> different locations.
> There is the main location, a children- and computer library as a
> thematic "branch" and several localized branches in some suburbs and
> villages around.
>
> You get one common user account for all of them and you can return media
> on any location and order any media to the location you want to get it
> (if you pre-order it).
> You can open an account on any location and so on.
>
> Therefore I would consider each "section" as it's own library, even if
> they share the user account system and their catalogue.
>
> Of course it is slightly different than the university library, which
> has only one section (here in Paderborn) but allows to get media from a
> whole network of university libraries around (if you pay some extra fee
> and wait for the book to arrive and so on), but for a map users point of
> view I don't think it's worth adding another tag for this.
>
> Nevertheless for thematic sections it may be useful to name/mark/tag
> them as such, to tell people this is a general library, that one a
> topical library for medical sciences and so on.
>
> regards
> Peter
>
> Am 01.12.2014 um 23:55 schrieb Mateusz Konieczny:
> >> "is there one name or different names?"
> >
> > Each part has its name, but it is name for this part of the library -
> > for example "Main lending library" (Wypożyczalnia Główna),
> > "Children's Section" (Wypożyczalnia dla dzieci).
> >
> >> "I believe multiple libraries aren't any problem"
> >
> >
> > For example - it will be displayed horribly on any map, as styles will
> > be unable to guess that these are sections of library, not separate
> > entities.
> >
> >
> > 2014-12-01 17:12 GMT+01:00 Martin Koppenhoefer <dieterdreist at gmail.com
> > <mailto:dieterdreist at gmail.com>>:
> >
> >
> >     2014-11-29 15:15 GMT+01:00 Mateusz Konieczny <matkoniecz at gmail.com
> >     <mailto:matkoniecz at gmail.com>>:
> >
> >         There is a large library with multiple sections (for children,
> >         for adults, foreign language
> >         books, reading room, movie/music borrowing, newspaper section
> >         etc etc).
> >
> >         There are separate accounts for separate sections, different
> >         opening hours. But it is
> >         managed by one institution, everything is in the same building,
> >         end it is generally considered as one entity.
> >
> >
> >
> >     is there one name or different names? IMHO separate accounts and
> >     different opening_hours already indicate some kind of separation
> >     (same operator doesn't mean it is the same "object"). On the other
> >     hand you state that you consider it to be "one entity", so more than
> >     one "amenity=library" would be wrong under that assumption.
> >
> >
> >
> >
> >         How one should tag it?
> >
> >         (1) amenity=library for both general entity and section
> >         (impossible for data consumers to
> >         understand that some are subsections)
> >         (2) use (1) and use some sort of relation to indicate hierarchy
> >         (de facto impossible to use
> >         for data consumers)
> >         (3) maybe introduce a new tag, something like
> >         amenity=library_section or something
> >         similar? Maybe library=section, without amenity=library and use
> >         amenity=libvrary to
> >         mark entire entity?
> >
> >
> >
> >     I think I'd prefer (3) as both, (1) and (2), are representing 2
> >     libraries (for what there are some indices in your description, but
> >     what you deny explicitly but saying it is "one entity").
> >
> >
> >
> >
> >         Note: http://wiki.openstreetmap.org/wiki/Tag:amenity%3Dlibrary
> has
> >         "A building can host multiple libraries. Please document the
> >         best way to handle this (with
> >         example) if you know a good solution. "
> >
> >
> >
> >     I believe multiple libraries aren't any problem, you simply won't be
> >     able to use bad short cuts aka use the same object for a building
> >     and a library function (which is a flawed approach anyway when it
> >     comes to details).
> >
> >     cheers,
> >     Martin
> >
> >     _______________________________________________
> >     Tagging mailing list
> >     Tagging at openstreetmap.org <mailto:Tagging at openstreetmap.org>
> >     https://lists.openstreetmap.org/listinfo/tagging
> >
> >
> >
> >
> > _______________________________________________
> > Tagging mailing list
> > Tagging at openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/tagging
> >
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20141202/dfdb8e66/attachment.html>


More information about the Tagging mailing list