Skip to main content

25Live

25Live logo

The 25Live connector ingests campus room bookings from 25Live (CollegeNET Series25) into the Mapped graph through R25 WebServices. It imports your 25Live spaces as Spaces under Buildings (or Sub-Buildings) and Floors, then continuously syncs each room's reservations as Calendar Events on that room's booking calendar.

The connector is read-only: it never writes to 25Live. Bookings can be forwarded downstream, for example to the Willow Events Destination Connector, to drive energy optimization and space-utilization use cases.

Use Cases​

  • Occupancy-driven energy optimization: condition only the rooms that are booked, including the setup and teardown time a reservation holds the room for.
  • Space utilization analytics: analyze scheduled usage per room and building to find under-used rooms and inform planning.
  • Unified scheduling view: combine 25Live bookings with the rest of your building data in one graph.

Configuration​

Auth Requirements​

The connector authenticates with an R25 WebServices username and password, sent as HTTP Basic auth on every request. Ask your 25Live administrator for a web-services account; read access is enough.

FieldRequiredDescription
Base URLYesYour instance's web-services root, ending in /run, for example https://webservices.collegenet.com/r25ws/wrd/<instance>/run. Test and production instances have different names.
UsernameYesThe web-services account's username.
PasswordYesIts password.

Saving this step checks the credentials before storing them.

Note: the connector only sees what this account may see. Rooms it cannot see are not imported. Bookings of events it may not read still sync, with no event state; they are synced as Confirmed.

25Live states every time with its UTC offset, so no timezone setting is needed.

Entity Import​

This connector uses the Mapped entities framework. Places are imported top-down in three steps. Read more on setting merge rules for updating entities in bulk.

Buildings​

25Live keeps a building record on very few spaces, so buildings are derived from space names. Most rooms are named CODE*ROOM, and the code before the * is the building: ALAM*101 belongs to building ALAM. A space that has a building record joins the code its building's other rooms use, and a space whose first word is a known code (MOSL East Lobby) joins that building.

Each building is named from what its rooms' formal names share (Alamance 101, Albertson Conference Room and Alamance Building 201 give Alamance), or from its building record. Correct any names in the grid.

Choose how each building links into the org graph by filling in one of two parent columns:

  • Site: imports it as a top-level Building under the selected org Site; or
  • Parent Building: imports it as a Sub-Building under an existing org Building (e.g. your authoritative CMMS/CAFM building).

If both are filled in, the Parent Building wins. The sub-building code defaults to the space-name code.

Floors​

25Live does not record floors, so they are derived from room numbers: ALAM*201 implies floor 2, 008E the ground floor (level 0). Levels are zero-based, matching Mapped. Only the leading digit is read, so fix rooms in buildings taller than nine floors in the grid.

Each floor carries a building-scoped level identity, so it resolves onto the floor you already have in Mapped at that level.

Rooms​

Load 25Live spaces as Spaces for the buildings you selected. Each room is pre-wired to the floor its number implies when that floor was saved; named rooms fall back to their building. Spaces whose name implies no building (lawns, fields, vehicles) arrive with Building empty: fill it in, or leave them unselected.

The space code defaults to the room number (ALAM*201 gives 201). Each room also carries its 25Live space_id.

Saving a room creates its booking calendar. Only saved rooms receive bookings; a booking in any other room is skipped and counted in the logs. Removing a room marks its current and future bookings cancelled, so they leave downstream calendars; saving the room again brings them back with the next daily sync.

Sync Settings​

OptionDefaultDescription
Lookahead (days)30How far ahead the polls sync bookings.
Event StatesAllSync only bookings of events in these states (Draft, Tentative, Confirmed, Sealed). Bookings of events the account may not read count as Confirmed.
Event TypesAllSync only bookings of events of these 25Live event types.

Filters decide what is synced from now on; they never cancel anything. A booking already synced keeps its last synced values if it later falls outside a filter (for example an event moving from Confirmed to Tentative while only Confirmed is selected), and changing a filter leaves bookings already synced in place.

Polling Schedule​

FunctionIntervalWhat it does
Current EventsEvery 30 minutesBookings created or changed since the previous poll, from a day ago through the lookahead.
Future EventsOnce per dayEvery booking from yesterday through the lookahead, a safety net for anything the 30-minute poll missed.
Deleted EventsEvery 30 minutesFinds bookings cancelled, denied or removed in 25Live and marks their events cancelled. See below.

Deleted bookings​

25Live gives no notice when a booking goes away: a cancelled or denied event's bookings, a cancelled reservation, or a room taken off a reservation simply stop appearing. The connector checks for these itself. When it finds one, the CalendarEvent stays in your graph with its callInfo set to Cancelled, and downstream systems that remove cancelled events, such as Willow, remove it. If the booking comes back in 25Live, the next sync restores it.

It finds them two ways:

  • Cancelled and denied events. Every poll asks 25Live which events changed. For each one now Cancelled or Denied, every booking of that event is marked cancelled at once.
  • Checking the bookings it synced. Once a day, every booking starting in the last 24 hours or later is checked; on a large campus that can take several polls. In between, each poll checks the bookings that changed since the previous one. A booking 25Live still lists is kept, and updated if it changed. One it no longer lists is looked up by reservation:
    • a reservation 25Live reports Cancelled is marked cancelled;
    • a reservation that moved to another date is updated there;
    • a reservation 25Live does not return, or one that no longer holds this room, is marked cancelled only if a complete read of every booking on its date also lacks it.

A reservation missing from a lookup is never, by itself, treated as deleted, because 25Live leaves out reservations the account may not read. A request that fails is never treated as a deletion either: those bookings are checked again on the next polls.

As a safeguard, if more than half of 10 or more bookings checked in one poll appear cancelled, the connector cancels nothing and reports an error instead, because cancelling can permanently remove events downstream. Confirm in 25Live whether the bookings were really cancelled, and contact Mapped support if they were not. Cancellations of whole events, which 25Live reports explicitly, are not held back by this safeguard.

So a booking removed without its event being cancelled, such as one cancelled occurrence of a recurring class or a room taken off a reservation, leaves Willow within about a day. For past bookings, run the job below.

Clean Up Deleted Reservations Job

Under Jobs, Clean Up Deleted Reservations checks bookings on demand and marks the ones cancelled or removed in 25Live as cancelled, deciding each one exactly as the poll does.

OptionDescription
Clean Up BydateRange checks every booking whose start time falls in the Date Range, past or future. reservationIds checks only the bookings of the 25Live reservation ids you list in Reservation IDs.
Allow Bulk CancellationOff by default. When more than half of 10 or more bookings checked appear cancelled, the job cancels nothing and fails, listing what it would have cancelled. Turn this on and run again only after confirming in 25Live.
  • Values that are not reservation ids (digits only) are skipped and listed in the job's log.
  • A reservation id that matches no booking from this connector makes the job fail after it finishes the rest, listing that id. The id may be wrong, the account may not see it, or it may have moved since it was synced: run the job by dateRange over its date instead.
  • If some bookings could not be checked or cancelled, the job finishes the rest, then fails and lists them so you can run it again.

Calendar Backfill​

Under Jobs, Calendar Backfill imports historical bookings for a Date Range on demand, a month at a time. Only active bookings are read: to remove cancelled ones from a past range, run Clean Up Deleted Reservations over it. Each run appears in the job history with its progress.

Mapped Concepts​

API to Mapped Entities​

25Live API ModelMapped EntityexactTypeNotes
(derived from space names)Building or Sub_BuildingBuilding / Sub_BuildingisPartOf a user-selected org Site, or (with a Parent Building) a Sub_Building isPartOf that Building.
(derived from room numbers)FloorFloorisPartOf its building, with a building-scoped FloorLevelIdentity.
Space (spaces.json)SpaceSpaceisPartOf its Floor when set, otherwise its Building/Sub_Building.
(per room, automatic)SpaceBookingCalendarSpace_Booking_CalendarOne booking calendar per saved room, linked via hasCalendar.
Space reservation (rm_reservations.json)CalendarEventCalendar_EventOne event per reservation per room. A reservation booking three rooms becomes three events, one on each room's calendar.

Each room Space carries a floor-scoped SpaceCode when its parent is a floor, and an ExternalIdentity scoped to this connector holding its 25Live space_id. Each CalendarEvent hasLocation its room and carries an org-scoped ExternalIdentity.

CalendarEvent fields​

GraphQL FieldSource
nameThe event name
descriptionEvent type, organization and expected attendance
startTime / endTimeThe reservation's start and end in UTC, setup and teardown included
callInfoThe event state (Tentative, Confirmed, …); Confirmed when 25Live gives none; Cancelled when cancelled, denied or removed
mappingKeycalendar_event/{space_id}/{reservation_id}
identitiesurn:25live:space_reservation:id:{space_id}/{reservation_id} (scope: ORG)

Sample Code​

Query rooms with their calendars and upcoming bookings

You'll need the connectorId of your 25Live connector, shown on the Mapped Console connectors tab.

Request
{
spaces(filter: { connectedDataSourceId: { eq: "your-connector-Id" } }) {
id
name
hasCalendar {
id
name
hasCalendarEvent {
id
name
callInfo
startTime
endTime
}
}
}
}