Dovid Bender
2020-Dec-11 19:28 UTC
[asterisk-users] New library portal description for the UK developer
Yossi, The goal is to be able to use the platform as a multi purpose system. I would rather have one interface and then have YouTube videos explaining how the system works rather then have multiple web interfaces. On Fri, Dec 11, 2020 at 1:56 PM Joseph Siegel <jsiegel at telecurve.com> wrote:> Hi Dan, > > I will let Dovid work with you on the back end, while I share how I > imagine the web side of things to look. We need to keep in mind that these > users are librarians, many older women who are not very tech savvy. I want > to have a system that displays a visual representation of how the IVR > works. I also want to have a simple mode and an expert mode. The simple > mode is what most libraries will use. It allows them to upload an initial > greeting, a menu of stories, and then each individual story. I am attaching > a file that I currently share with them to help them understand how the > system is structured so they know what files they need to record. What I > imagine is a web based portal that has similar "bubbles". One for the > greeting, one for the menu, and then the ability to add up to 99 for each > story that corresponds to the number someone presses Within each bubble, > they could either upload a file, or record one directly on the web, > playback to hear the quality, delete if they need to replace. > > > The expert mode would have a similar structure but allow for a drag and > drop (or other simple to use system) so that they could create submenus. > See page 2 on the attached illustration that I use to demonstrate that > function currently. > > Obviously, we also need an admin portal to create and manage accounts. As > Dovid discussed, we will want to add features *down the road*, for > example, in a story bubble they could insert a web stream instead of > uploading/recording a file. Our initial goal is to have a portal that > allows both the simple and expert mode so our product can run on its own > without having to manually send and load files as we are doing today. > > On Tue, Dec 1, 2020 at 3:52 PM Dan Jenkins <dan at nimblea.pe> wrote: > >> Hi Dovid, >> >> Sorry for missing your last email - it got mixed up with a load of >> broadcaster.vc interest. Yup totally - web ui that enables recording of >> prompts, building up an IVR etc... >> >> How did you want to handle the backend of the phone system? All database >> driven and youd code up the IVR? Or do you want it all handled with >> something like the ARI? >> >> Dan >> >> >> >> On Tue, Dec 1, 2020 at 7:12 PM Dovid Bender <dovid at telecurve.com> wrote: >> >>> Dan? >>> >>> >>> On Thu, Nov 26, 2020 at 5:01 PM Dovid Bender <dovid at telecurve.com> >>> wrote: >>> >>>> Dan, >>>> >>>> Please see below which is what we want in simplified terms. Does this >>>> go along what I explained to you on the phone? We could go into greater >>>> details such as call records, graphs for the admins etc. >>>> >>>> >>>> >>>> On Wed, Nov 25, 2020 at 11:58 AM Joseph Siegel <jsiegel at telecurve.com> >>>> wrote: >>>> >>>>> >>>>> >>>>> We provide libraries with Dial-A-Story services. Each library gets a >>>>> dedicated phone number. When people call the number, they hear a greeting, >>>>> followed by a menu of stories to listen: >>>>> >>>>> Demo - 732-313-0099 >>>>> >>>>> Some libraries have submenus - for example, to listen to children's >>>>> stories press 1, to listen to adult stories, press 2 - Demo >>>>> 862-910-1100 >>>>> >>>>> Currently, libraries record their stories using whatever software they >>>>> have, and then email us the audio files. >>>>> >>>>> We would like a portal that will allow them to record and play >>>>> back their audio files, along with the ability to create dynamic menus. So >>>>> a menu system like the first demo # above, or submenus like the second. It >>>>> has to have an easy to use GUI since most users are going to be librarians >>>>> with basic computer knowledge. >>>>> >>>>> Essentially, they start with a blank plate and easily build menus and >>>>> add stories to those menu options. >>>>> >>>>> >>>>>-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20201211/7ecf2018/attachment.html>