as of version 2.15.5
A root server is a database, where meeting information is stored. There are 2 typical uses, a Zonal Forum or region ( known as parent service bodies ). The main “parent” root server can be set up so member service bodies ( Regions & Areas ) can independently own the meeting data for their meetings.
Each member service body can enter in meeting data like day of week, Group name, Meeting format, Location, extra info for meetings ( like use side door ), Virtual Meeting link and passcode, publish or unpublish ( if a group is temporarily not meeting ). Once a meeting is created, edited or unpublished, any website using Crouton, Bread ( meeting directory PDF ), Upcoming meetings and List locations will be able to display that change. It will also update for your YAP phone-line meeting listings.
SuperUser roles of a BMLT root server can export data and submit to NA World Services. This is an important feature because the data in the root server is supplied to NAWS for use, it is highly suggested that any member service bodies use the root server for submitting new meetings and updates to NAWS. An example would be: an Area BMLT admin creates a new group in the root server, publishes the meeting, the Root Server Admin creates an export for NAWS and submits the file to NAWS. The Tech lead at NAWS imports the data and assigns a World Committee Code for the meeting, sends the new committee codes back to the Root Server Super Admin, who in turn imports the data back into the Root Server. If there is a deviation from this there will be a duplication of information and provide confusion at NAWS and potentially delay meeting information being displayed on NA.org and the NA mobile app.
When setting up a Root Server or updating the NAWS World Committee Codes this can be done from the Server Administration tab. You must be logged in as a Service Body Administrator to import this file. To get a file email firstname.lastname@example.org and ask for your Region, Area’s NAWS export file.
When importing the file to an existing BMLT Server this will update the World Committee IDs only. It will not change the address, city, zip, name or other information.
Login to your BMLT Server with admin credentials. After logging in you can select the service body to add/edit/delete a meeting.
After selecting the service body look for the meeting to edit or click on the “Create A New Meeting” button.
To edit click anywhere on the meeting information line. This will open the meeting to the basic tab. Here you will see the meeting is published checkbox. Checking it will “publish” the meeting and make it appear on schedules, websites and apps. Unpublishing it will remove them from those lists.
The meeting id is generated when the meeting is added to the BMLT Server is unique to that server.
Meeting Name can be will take any letters, numbers or special characters, no html though.
Weekday will allow you to pick the day of the week the meeting is occurring.
Meeting Start Time, this is where you set or change the start time of the meeting. There is also a noon and midnight selections in this list.
Duration is for the length of the meeting.
World Committee Code is the text that NAWS gives you to identify the meeting. All codes for groups start with a “G”, Areas with an “A”, Regions with a “R” and Zones with a “Z”
Service body will display the service body that this meeting belongs to. If you have a meeting/group that is changing service bodies have the an admin with more rights, RSC for an ASC simply change the service body from one to another. This will eliminate duplicates when service bodies create a meeting instead of switching.
Meeting email contact allows you to have a email displayed in crouton or meeting schedules.
Follow the same steps as above and find the meeting you want to delete. Click on that meeting then click on the red “Delete This Meeting” button.
With the onset of virtual meetings there are ways to add that information to a BMLT Server that will help display and convey that information in the various applications that are leveraging the a BMLT Server.
More information can be found in this Blog post.
When adding a meeting that is a virtual/phone meeting or hybrid you can use the Phone Meeting Dial-in Number and Virtual Meeting Link fields on the location tab when adding or editing a meeting.
The Virtual Meeting Link field accept urls with the http or https protocols. When you add this link to the field it can be displayed in the various applications. The “Virtual Meeting Link” field is designed to hold the join link for video-capable virtual meetings software such as Zoom and BlueJeans.
The Phone Meeting Dial-in Number field accepts a phone number that can be used to join the meeting. These fields have
been added to the NAWS Export, ensuring NAWS has the most up-to-date
information about these new location-centric virtual meetings.
If your address points to a large area on the map and you want it to point to a specific spot you can move it.
Click on the Location Map link and this will open a map with a pointer at the location Google has picked for that address.
This map can be zoomed in, changed to Satellite view or anything else you can do with a Google map.
Switching to satellite view will allow you to drag the marker to a specific building, parking lot or place in a park for an outside meeting.