Mobile AppContacts: Johan Olander (European Spallation Source ERIC) If you know of other recent tutorials or related materials, please add them to the appropriate places on the page and create a new subheading if needed. OverviewThis page intend to describe the current tools support and recommended. See the Mobile App Working Group for more details on support and JACoWs intentions. There is a recommended App Vendor available and presumed for this instruction. There is also a need to utilise a data extract software called SPMS_extract.py. The architecture is based on reuse of SPMS data and if possible should be kept that way due to the state of the Indico migration. The App offers in place upgrades for conference series. Preparartions & ConditionsThe toolset is developed to be used with the AppInConf offering, it would very likely be quite pointless with another app-vendor. Contact details for the company are available. One should pay attention to the discussion of the Mobile App Working group before experimenting too much which the agreed feature base. This process presumes that you have setup your SPMS according to the recommended standard process. The data export is pretty absolute, this means if you don't have proper sessions codes or proper time slot set up it will fail. For IPAC'17 this acted as a data verification tool and led to a better SPMS setup and a faster way for us to spot problems. DataThe benefit of using this process is that the vast amount of data being tracked per conference. Instead of recreating this somewhere else we rely on SPSM to provide a single source of truth. Making updates and changes easier to manage and track. This following information is extracted and parsed from SPMS:
For IPAC'17 there was 5283 Authors tracked, 10 MC's and 8 rooms and 1581 Schedule events. Due to these big numbers manual change is almost impossible to get right. On top of this the schedule and abstracts are also exported. ToolsSPMS, the spsm_extract script and the CMS from AppInConf are the necessary parts. A local machine to run the script on is also necessary. SetupThere are two fields that needs to be modified inside the script.
The script was originally developed running with Python 3.5 (as part of Anaconda3-4.1.1-Windows-x86_64) and will most likely work on any version of python3, and can be modified for python2. There are some dependencies needed, please use google (or bing if in China) for guidance.
Run the script by invoking: 'python spms_extract.py' The expected output is: config.plist, scheme.plist & one file per abstract WorkflowIPAC'17 being the pilot for this vendor selection there is a lack of structured data transfer between SPMS and the App platform. A couple of pieces of data need to be catered to, namely:
These are put into excel files and uploaded through the CMS. The Floor plan are uploaded to, and exhibitors and other things are mapped out with a GUI. The extracted data from the script is zipped into an archive and sent to the vendor. The recommendation is that the App should be made available for download C-1 month, so as soon as SPMS has data enough to produce the abstract booklet they you are ready to go. IPAC'17 ended up doing 21 data transfers, mostly for early bug fixes but also due to some data errors. Specifications
Current FeedbackIPAC'17 did an extensive survey, here are the results for the mobile app. General Usability Feel free to add your motivation for supporting (or not supporting) a paper-less conference.
Statistics
|