Need suggestions on room reservation system. Posting it as I couldn't find a similar question here in SO.
Question: Can I use wordpress and create my own plugin using php/mysql for a very simple and straight-forward room reservation system (4 page workflow)? If not what are the possibilites, Please suggest.
If the post is not in the right forum, please feel free to close it or re-direct me.
Background: I work part time for a non profit organization (I dont get paid, it's just a service to the community during my free time). They own a small property with about 20-30 rooms onsite and manage their room reservations, manually with Google drive.
I've suggested them to build an online portal for reservation. This is a service project, to enhance my technical resume as well as help someone.
My technical abilities - HTML, CSS, VB, SQL, PL-sQL (A long time ago) and I'm an automation tester so very good with programming skills.
Project deadline - 4 to 6 months. (I'd be spending about 15 hours/week)
PS: If this is beyond my capabilities I will be asking them to outsource.
Did you look at SourceForge, etc, to see if you can get a ready made system for free?
You may have to tailor it a little, but it might still be the quickest & easiest way to get somethign up & running. Your skills seem fine, though (VB is fine for a Windows app, you would want PHP for web-based).
Take a look at
Meeting Room Booking System is a free, GPL, web application using PHP and MySQL/pgsql for booking meeting rooms or other resources.
Meeting Room Reservation System, a mock project for study purpose.
phpScheduleIt, a web-based resource scheduling system
OpenRoom provides a simple online interface for managing and reserving rooms
RoomTimes is a php written application with which you can manage the rooms of any organisation
or you might want to google for others
Related
Hi Overstock flow peoples,
I've been in the startup/digital marketing scene and know some things on analytics, html/css, and marketing automations and have recently picked up some SQL/Tableau. Im coming here looking for possibly help/recs on connecting a marketing system/inflow that uses Fare Harbor/Mighty Call/Life 360 and I'm wondering if I could automate things with Zapier (or some other platform), or if I'd have to do it all with development or using APIs or something.
I work with a company that does some travel taxiing/luggage help for travelers. Im looking to see if Zapier (or any other system) would be able to automate some tasks.
So clients book through Fare Harbor, their data goes into our system through Mighty Call, and we give updates to the clients on the drivers ETAs manually through Life360 (like the owner actually TEXTS people directly).
Would anyone here know if there's a way to use Zapier to automate the ETA/communication updates of Life360 through Zapier? (Or would I have to develop something completely on its own to do this?). Or know if there's any other type of software to do this immediately off the top of your head? (etc). Otherwise we have to text all these updates manually and we're trying to get away from doing things that way.
Sorry if this comes off as a rookie post, as its my first direct post on Stack Overflow, although I've used this website a number of times to configure CSS before and other ish (and this isnt my first rodeo). Any advice or direction that could be given would be IMMENSELY helpful.
My company uses Quick Books Online for its accounting, and that's where we go to log our time against projects. In an effort to make time entry easier, and a way to learn how to write a Windows 8 Metro app, I thought it would be a useful project that simplified time tracking, application that could automatically submit my time to QB. The thought would be users would use their own QBO logins so it would be able to see their time entries.
I have been looking around the api for QBOE and can't seem to tell if its possible to connect to a QBOE account with non admin credentials. Is what I am thinking even possible?
No, this is not possible. You will need something in the middle to talk between QB and your application.
There are a number of different timesheet apps on appcenter that you might look at. https://appcenter.intuit.com/category/time-tracking
The IP addresses logged in by the Drupal 6 core "Statistics" module are not being displayed by the AW statistics displayed by my hosting server (hostgator). I am not able to comprehend why and which statistics are more reliable ? Also I would request some light to be shed on the best practices to monitor a Drupal 6 website. Thanks for your help people.
the best free analytics packages are google analytics and piwik. i personally would go for piwik.
Heres a good A vs B
Also worth checking out the goal tracking if thats what you need as i believe this is something thats missed out of the 1st link - maybe this was done before goal tracking was integrated
As for the mentions of funnels analysis, yes piwik might not do that yet, but its on the roadmap. Its worth factoring this into your plans - do you want to track specific the funnels of customers to conversion? e.g. the % of x people and the route they took to purchase?
Another A vs B
Alright. So I am new, I know my way around html pretty well, and have gotten by for a while now doing so. But today I am presented with a seemingly simple issue.
My client needs the ability for users to create their own LOGIN/PASSWORD, my client wants to be able to MANUALLY approve visitors. And he want to be able to track how many times they login.
The login section will just be about 4 pages of PDF file downloads.
I cant imagine this is the hardest thing in the world, I just have no clue where to even start. Perhaps there is a code already written, as things like this are done every day using forum technologies...
Please help!
It may also help to mention that I am using Dreamweaver cs4 on a MAC
I'd check out Ruby on Rails if I were you. It's pretty easy to get something quick up with it that you can have users create accounts with that send e-mails to the client with approve/reject options, and be able to track downloads and users via MySQL or other databases.
I've found Agile Development with Rails to be a great source of info on how to do stuff like this (they do an online bookstore as the book's example) and with a little modification I think it should work for what you say you want to do (and the book is pretty cheap as far as programming books go).
If you want just really basic static login features without lots of coding, you can start with Password protecting your pages with htaccess. You can password protect directories like this without any effort at all. This way, you can be sure that your login routine is secure.
Then, you can continue with advanced features like account administration and login statistics. These will require some programming skills.
Tracking count of user logins should be easy too. You can put simple PHP code to the source of protected pages that will save the info about login to the database. This will require you to study some basics of databases. You can use plaintext files which is not as clean but much easier and it will allow you to export info for your client more easily.
If you want to do it profesionally, you should invest in learning about web development or hire someone to do it for you. These tasks might not be trivial.
Have you worked with PHP, ASP.Net or some other web language yet? What you're trying to isn't too difficult in the grand scheme of things but it may be somewhat challenging if you haven't programmed before and/or haven't had any experience with web development.
(P.s. Alter your question as a response and comment on my answer when you're finished.)
As you are looking into Ruby on Rails, take a look at bort which is a RoR app skeletton with RESTful authentication included, it should help (Chris Bunch answered on the general RoR question).
There is also this bort fork. There is also Authlogic which may be easier to work with.
Have a look at the ASP.net Membership provider and also the login controls which provides the UI for the login as well as registration screens out of the box.
Here is a Multipart Series on ASP.NET's Membership, Roles, and Profile
If this is too complex than probably you can also design you application from scratch using ASP.net. If you don't know asp.net than the best place to start is www.asp.net it has several videos and tutorials which would help you get going soon.
I have a little experience with bug tracking systems such as FogBugz where help tickets are issues are (or can be) bugs, and I have some experience using a bug tracking system internally completely separate from a help center system.
My question is, in a company with an existing (home-grown) help center system where replacing it is not an option, how should a bug tracking system (probably Mantis) be integrated into the process?
Right now help tickets get put in for issues, questions, etc and they get assigned to the appropriate person (PC Tech, Help Desk staff, or if it's an application issue they can't solve in the help desk it gets assigned to a developer). A user can put a request for small modifications or fixes to an application in a help ticket and the developer it gets assigned to will make the change at some point, apply their time to that ticket, and then close the ticket when it goes to production.
We don't currently have a bug tracking system, so I'm looking into the best way to integrate one. Should we just take the help tickets and put it into the bug tracking system if it's a bug (or issue or feature request) and then close the ticket if it's not an emergency fix? We probably don't want to expose the bug tracking system to anyone else as they wouldn't know what to put in the help center system and what to put in the bug tracker... right?
Any thoughts? Suggestions? Tips? Advice? To-dos? Not to-dos? etc...
Have a promote to bug button on the help desk system, that publish the ticket on the bug tracker, with the appropiate reference info.
Is this for a production system with end users reporting bugs, or for issue resolution during QA?
If it is the former, some live person should triage the help desk tickets and only log as a bug what really is one.
If it is the latter, you should not integrate at all.
Well, it's a tradeoff.
We use separate systems for help desk tickets and for bugs.
Pros:
Workflows & requirements will probably different between devs and help desk, you can choose a system for each that fits requirements (e.g. fields that are only relevant for dev or for help desk, different kinds of email integration).
Clear responsibilities: Help desk handles tickets, devs handle Bugs.
Cons:
Integration will not be quite seamless (you need either automatic integration, which does not always exist, or manual back-forth links, which people may forget).
So far, we're quite happy with two products. It is occasionally annoying to have to paste links or close a ticket and a bug, but usually tickets and bugs are handled by different people anyway, so it's not a big deal.
One product might also work well, if you can find one which fits everyone's workflow.
In the raiseaticket help-desk system, we create a separate workflow for Prod, Dev and Bugs. The ticket is assigned to relevant group based on the nature of the issue. These tickets are not exposed to any other group. So, we can do a workaround in our help-desk portal system for the bug tracking.
For anyone in 2022 (and beyond) looking to integrate a help desk system and bug tracker, DoneDone does this well.
We use a DoneDone mailbox for general customer support (both via our support email address and the contact form on our website). It lets you have private discussion on emails, along with allowing you to assign, prioritize, tag, and create/change statuses on them (e.g. "Open", "In Progress", etc.)
We use DoneDone projects to manage internal bugs/issues/tasks.
DoneDone lets you connect support emails (the helpdesk part) to internal tasks (the bug tracking part) as well. So, if your company has distinct support and client-facing people while also having internal devs and you want to separate their work, you can create any number of subtasks from an incoming conversation.
Even if your company isn't that stratified, it's nice to be able to create bugs with their own workflows separate from a helpdesk ticket (which has its own workflow).
More info at https://www.donedone.com