I have an interesting situation here this time.
This more of a conceptual question, less of a technical code question.
I need to have an 'availability calendar' for a new web application.
The calendar needs to allow users to easily choose dates that are unavailable at the cottage (and update them in the future).
Any ideas for a calendar or a simple and effective method to do this would be great.
I've seen various jQuery and similar calendars, however none of them seem to make it easy to select dates in various months, etc.
Thanks in advance,
Craig
One way to make a calendar easy to use for the selection of date ranges is to imitate certain aspects of how a roulette board is used to select ranges of numbers. For example, clicking on a region either side of a week would select the whole week, while clicking on a region above/below a particular day of the week would select all days of the week for that month.
Roulette - this came to my mind
http://www.marca.com/deporte/futbol/mundial/sudafrica-2010/calendario-english.html
Related
i'm messing about with powerapps and attempting to build a small app that adds all my exams into my school's calendar as this will save me (and other students) a lot of time.
at the moment i have already managed to get all the required data from the excel file that contains all exams with their dates, locations, times and much more irrelevant information. this data is filtered to only include the exams for me (and technically all other engineering students if i make it public)
i've stored it in a collection and have no problem using it.
the issue is the outlook/office365 connector as im not shure it can do what i'd like it to do.
Office365.V2CalendarPostItem(calendarSelect.Selected,test.'Cursus Omschrijving',test.'Datum/Date',test.Tot,{Location:test.'Locatie/Location'})
i've put up a calendar selection dropdown thing as i dont know if all calendars are the same so you can select the right one. calendarSelect.Selected is the result of that. test.'Cursus Omschrijving' is the title of the exam. the date bit is, well, the date and start time, and test.Totis the end time.
the issue is Office365.V2CalendarPostItem expects only one item at a time really. powerapps complains about it recieving a table and not text or a date as it expects.
Do any of you know if it is even possible to do what im planning(bulk adding calendar items) or is powerapps not capable of this and i need to switch over to a more powerful language?
This is my first time in the forum so if I made any mistakes please let me know.
So I have to do a research work for school and I am having a little bit of a problem finding a data set that meets all my requirements. This is for my database class. I have been looking the whole weekend and I have not been able to identify any valid source.
Still after all that I have been able to find nothing.
I was wondering if you could help me; perhaps there is a more flexible website to help me narrow the search; or a specific website with the information..
Here are all the requirements:
The data set must be from a legitimate source (e.g., the us gov, a state agency, a university).
The data set must measure something by date and by zip code. in essence, the data set can contain just 3 fields (date, zip code, measure).
The date range must be at least 10 years and span.
The level of granularity of the date must be at least by month, and in the format of YYYYMM or YYYYMMDD.
Zip code must cover all fifty (not 58) states.
Anything except weather
Thanks a lot in advance for the help
You can try the U.S. Census Bureau, there are several datasets that should match your need, although there is probably more information than the minimum you need: that is likely to be true in most real-world examples.
I'm trying to design a database table for storing events that occurs at different intervals,
--daily, eg. everday around 10am
--every tue,mon and wed of a week,
--monthly, eg. 1st of every month
--twice a month, eg. 3rd and 4th of every month
How can I achieve this with simple database design. Any help, suggestion is appreciated. Thanks in advance!
You are mixing up the UI with the backend. You need to create the following tables:
intervals(interval_id, name, repeat_time_span)
events(event_id, interval_id, name, created)
You need to implement the CRUD to handle intervals and events insertion, modification, deletion and view. You need to link UI controls (like a form and a grid) to enable user interaction with the events and intervals and to implement any advanced logic regarding those.
I'm creating a calendar application in which each date has one of 3 states: available, maybe available, and unavailable. Trying to figure out the best schema for this situation.
One thought might be to have a UserDate model with a field state. The problem with this is that the DB will have #-of-users- x 365 rows for each year - seems like it would grow too quickly for a modestly sized app.
Another thought might be to have a default state, and only create a UserDate object when the user has signified that their availability on that date is different from the default. This seems convoluted though.
Has anyone dealt with this situation before? Any suggestions on the best way to go about this?
When you create a new user, you do not want to be inserting records for the next 50 years of their life. Only creating the UserDate object when there is a non-default value is what you should do.
You could consider storing a range of dates for a user if you are likely to have lots of consecutive dates with the same status. For example, if they are unavailable for all of December, then this could be represented as a single row.
Think about the sort of information you want to extract from your database, and how difficult this will be with each of your possible designs.
I have an interesting problem trying to represent complex schedule data in a database. As a guideline, I need to be able to represent the entirety of what the iCalendar -- ics -- format can represent, but in a database. I'm not actually implementing anything relating to ics, but it gives a good scope of the type of rules I need to be able to model for my particular project.
I need to allow allow representation of a single event or a recurring event based on multiple times per day, days of the week, week of a month, month, year, or some combination of those. For example, the third Thursday in November annually, or the 25th of December annually, or every two weeks starting November 2 and continuing until September 8 the following year.
I don't care about insertion efficiency but query efficiency is critical. The operation I will be doing most often is providing either a single date/time or a date/time range, and trying to determine if the defined schedule matches any part of the date/time range. Other operations can be slower. For example, given January 15, 2010 at 10:00 AM through January 15, 2010 at 11:00 AM, find all schedules that match at least part of that time. (i.e. a schedule that covers 10:30 - 11:00 still matches.)
Any suggestions? I looked at How would one represent scheduled events in an RDBMS? but it doesn't cover the scope of the type of recurrence rules I'd like to model.
In the end, this post was most helpful:
iCal "Field" list (for database schema based on iCal standard)
We decided to follow the iCal model pretty exactly since the guys who wrote that standard had a great feel for the problem domain.
The way I did something similar to this was to have two tables. If an event had no recurring pattern, then just store the date, start time, and end time. Your query checks if the time your searching for is greater than the start time of any entry and less than or equal to the end time of that same event.
For recurring events, I'm not too familiar with how iCalendar stores recurrences, but if you store each event by day of the week (you might have to have multiple rows for a single event if it repeats on more than one day a week), then search it almost the same way as the above table. For stranger recurrences like the third Tuesday of the week, you could have an extra column describing the specific condition. I might be able to give you a better answer for this if you could tell me more about how ics represents that kind of recurrence.
I hope that helps. I don't have much time right now. You can contact me later if you want to discuss this. I'm currently in Missouri so my availability for the next week is going to be erratic.
This might be a trivial solution, but what would be the drawbacks of adding a column that defines the recurrence of the event (i.e. every x weeks, annually, weekly, etc) and using that as the result criterion?