Hi Michael, We go with /spaces, which fits our needs currently, as we're using our system to reserve not just rooms but also some physically open spaces in our locations, with the potential to add different types of spaces for reservation. It's also short and easy to circulate on print materials. We originally used /room_reserve, which would translate to roomreserve for the needs you've laid out (excluding underscores and hyphens is a smart move).
Sincerely, Katherine Lynch --- Katherine Lynch Library Web Developer Drexel University Libraries Drexel University 3300 Market Street W. W. Hagerty Library Philadelphia, PA 19104 Tel: 215.895.1344 | Fax: 215.895.2070 drexel.edu/library On 11/30/12 9:05 AM, "Michael Schofield" <[email protected]> wrote: >What¹s up everyone, > > > >We are homegrowing a study room reservation system and we¹re within a week >of making it live‹but still in beta‹to the public. Right now, on our >staging >box, our URI looks like something.library.nova.edu/room-res. /room-res >doesn¹t mean anything, to me. The public URI will be similarly long, like >somethingelse.library.nova.edu/whatever. > > > >Any recommendations or experience with your own reservation links? IMHO, >it >should be simple, since the link is already going to be on the long end. >Right now I¹m vying for /reservations, but TBH this system is just for >public study rooms and not for our larger conference rooms I¹m not sure >our primary users [the students and faculty] will care, but we¹ll >definitely >be reminded of that technicality by other librarians J. I don¹t like >/studyrooms, but it¹s the best I¹ve got since I¹m avoiding hyphens. > > > >Just picking your brains. Thanks! > > > >Michael Schofield(@nova.edu) | @gollydamn | Front-End Librarian à >www.ns4lib.com > > > >
