Prismm Frontend Docs

Appearance

Terminology/Glossary: ​

Event/Occasion ​

Event/occasion are the highest layer, and they are the first thing made. Events hold floorplans, can have a venue assigned to them, vendors, host, and more. Events have a few set parameters that are mandatory to them (expected number of guests, date, and type). Users have a set number of events they can create, and have to pay to get more.

Layout/Floorplan ​

A floorplan is an instance of a hall. Floorplans can have objects, shapes sizes, guests assigned to these objects etc. Floorplans are unique.

Templates ​

Templates are saved floorplans that can be used to “quickstart” floorplans. Any floorplan can become a template by being saved, and templates can also be “published for widget”, which allows you to see them in Widget.

Widget ​

  • Vision
  • A widget (version of vision) with vendorid

Vision ​

  • Matterport
  • Connect
  • Sharable Link
  • More

Showcase ​

A product/marketing name for Vision.

VisionPlus ​

Not matterport (usually also called realview), it costs more and allows you to move more around the space. As opposed to Matterport, we have full control over it.

Matterport ​

Company we pay, and also type of scan we use for events. You have points in the floorplan u can move to and its not free moving. We have less control, and its harder to add and change features in Matterport. Matteport is also known as Vision.

Venue ​

A type of account, is a physical location where you can host events usually.

Vendor ​

A type of account, can be caterer, band, etc.

Host ​

A type of account, the person throwing the event.

Private Collection ​

Private collections can either be the private collections of specific venues, which are the items that venue has to offer, or other vendors you can add as private collections that don’t appear in the regular dropdown (specific rental companies for instance).

Entourage ​

Just a way to add more people to an event.

Designer ​

Ops, I think specifically the seating page.

Ops ​

Ops.prismm.com, the main product, where you can create and edit events and other stuff.

Venueverse ​

Dev name for an app called venueverse which replaced the non vendorid parts of Widget, it allows you to either check out a few venues and see their halls and templates or use the connect[connectlink] part.

Admin ​

The Admin dashboard is a separate application that is used to manage users, events, and other data (like adding objects/chairs and looking up stuff).

Studio ​

Not relevant anymore, but was an application that was used to monitor leads generated from venueverse.

Exvo ​

Not relevant anymore, it was an application for virtual events, that company has since been split off and is called Meetaverse now. We support them, and they (supposedly) use our SDK so we can’t break exvo functionality. Exvo has a lot more users concurrently so it requires more optimizations, and they make use of complex entities to handle stages and booths.

Meetaverse ​

The company described above, it consists of a few former employees and investors.

VR ​

We used to have a VR application that was like Exvo, but it has since been discontinued and is not updated.

Extluid ​

Extluid is how connect events work, it is used to hide the occasionid and is generated in sql when a user clicks on share an event in Ops.

Brand Objects ​

Objects that are from a certain brand, they behave slightly differently from regular objects.

Custom Objects ​

Custom objects are, as the name implies are custom. They range from shapes to ceremony chairs. These objects can usually be edited significantly more than the other objects.

Hall ​

A hall is an area from a venue scanned. You can’t place objects on a hall, a floorplan is an instance of a hall.

Map ​

The maps are usually part of the url to get the svg of the hall. The Svg of the hall just describes it in svg form.

Tlatfile ​

The tlatfile (this might not be relevant soon) describes all the information hall3d needs in order to load the event properly.

TypesFile ​

The types file has most of the data about the occasion (floorplans custom objects etc). Theres also the layoutobjects file which has all the objects.

ASMP ​

Stands for nothing it’s a json file and describes the walls needed to draw the fakeview in 3D.

Fakeview ​

Not Realview (visionplus) or Matterport and is transparentish walls.

ASM ​

FBZ files zipped (3d model object files)

An extluid link generates this, it’s a way for Vops to communicate with vision. They share calls in this version and see real updates of the event made in ops.

Agora ​

The voice chat/video chat provider we use.

Firebase ​

The realtime provider we use, firebase is used to communicate between Ops and Connect, and between connect users.

Databank ​

A former provider of SQL we migrated from to Azure.

Cold Fusion ​

The language used to write SQL queries in databank its old and hard to use.

SQL ​

SQL Database.

MongoDB ​

NoSQL Database. We use Cloud Atlas MongoDB specifically.

Cloudinary ​

The CDN provider we use.

Afr/Cort ​

Aka Public Private Collections, these are the rental companies everyone has “on” by default without adding specific venues/vendors.

API/Integration ​

The API is used by third parties to create occasions, or for other types of integrations with allseated (like exporting cort specific skus etc).

Account ​

An account can have multiple users inside it.

User ​

a user inside an account.

Big Account ​

I don’t know

Multivenue ​

A legacy term, which big account is going to replace