org.models.resource
Classes
Manages a list of resources. |
|
A resource holds a single calendar with allocations and reservations. |
|
A resource holds a single calendar with allocations and reservations. |
|
A resource holds a single calendar with allocations and reservations. |
Module Contents
- class org.models.resource.FindYourSpotCollection(libres_context: libres.context.core.Context, group: str | None)[source]
Bases:
onegov.reservation.ResourceCollection
Manages a list of resources.
Returns the date range set by the fullcalendar specific params.
The reservations associated with this resource and user.
The session id associated with this resource and user.
Returns a query which joins this resource’s reservations between start and end with the tickets table.
- class org.models.resource.DaypassResource[source]
Bases:
onegov.reservation.Resource
,onegov.org.models.extensions.AccessExtension
,onegov.search.SearchableContent
,onegov.org.models.extensions.ContactExtension
,onegov.org.models.extensions.PersonLinkExtension
,onegov.org.models.extensions.CoordinatesExtension
,SharedMethods
,onegov.org.models.extensions.ResourceValidationExtension
,onegov.org.models.extensions.GeneralFileLinkExtension
A resource holds a single calendar with allocations and reservations.
Note that this resource is not defined on the onegov.core declarative base. Instead it is defined using the libres base. This means we can’t join data outside the libres models.
This should however not be a problem as this onegov module is self contained and does not link to other onegov modules, except for core.
If we ever want to link to other models (say link a reservation to a user), then we have to switch to a unified base. Ideally we would find a way to merge these bases somehow.
Also note that we do use the ModelBase class as a mixin to at least share the same methods as all the usual onegov.core.orm models.
- class org.models.resource.RoomResource[source]
Bases:
onegov.reservation.Resource
,onegov.org.models.extensions.AccessExtension
,onegov.search.SearchableContent
,onegov.org.models.extensions.ContactExtension
,onegov.org.models.extensions.PersonLinkExtension
,onegov.org.models.extensions.CoordinatesExtension
,SharedMethods
,onegov.org.models.extensions.ResourceValidationExtension
,onegov.org.models.extensions.GeneralFileLinkExtension
A resource holds a single calendar with allocations and reservations.
Note that this resource is not defined on the onegov.core declarative base. Instead it is defined using the libres base. This means we can’t join data outside the libres models.
This should however not be a problem as this onegov module is self contained and does not link to other onegov modules, except for core.
If we ever want to link to other models (say link a reservation to a user), then we have to switch to a unified base. Ideally we would find a way to merge these bases somehow.
Also note that we do use the ModelBase class as a mixin to at least share the same methods as all the usual onegov.core.orm models.
- class org.models.resource.ItemResource[source]
Bases:
onegov.reservation.Resource
,onegov.org.models.extensions.AccessExtension
,onegov.search.SearchableContent
,onegov.org.models.extensions.ContactExtension
,onegov.org.models.extensions.PersonLinkExtension
,onegov.org.models.extensions.CoordinatesExtension
,SharedMethods
,onegov.org.models.extensions.ResourceValidationExtension
,onegov.org.models.extensions.GeneralFileLinkExtension
A resource holds a single calendar with allocations and reservations.
Note that this resource is not defined on the onegov.core declarative base. Instead it is defined using the libres base. This means we can’t join data outside the libres models.
This should however not be a problem as this onegov module is self contained and does not link to other onegov modules, except for core.
If we ever want to link to other models (say link a reservation to a user), then we have to switch to a unified base. Ideally we would find a way to merge these bases somehow.
Also note that we do use the ModelBase class as a mixin to at least share the same methods as all the usual onegov.core.orm models.