Closed Bug 668322 Opened 13 years ago Closed 13 years ago

Enable and enforce MM/DD/YYYY date format for MDN Events calendar/table

Categories

(developer.mozilla.org Graveyard :: Wiki pages, defect)

x86
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: jay, Unassigned)

Details

(Whiteboard: p=3 c=events)

I propose that we consider having a "Start Date" column and "End Date" column so we can use MM/DD/YY or YYYY as the date format and enable sorting by date(s).  If that's too much to ask, we can leave the date field alone and at least enable sorting by the other columns (if that's easy enough).

Christian:  I know Google forms can be a pain when changing fields/columns after there is data already in there, so not sure it'll be possible to add a new column without messing things up.   Worth trying?

Luke:  I'm assuming the code would be able to handle a new column regardless of where it is in the spreadsheet, right?   If we add an "End Date" field, I'm guessing it will show up as the last column in the spreadsheet.

If we decide to try this, let's do it for 0.9.8 and test on stage9 with a new form/spreadsheet... so we can consider migrating data over to that new doc.
Target Milestone: --- → 0.9.8
Christian, if you want to try a new spreadsheet and give me the url I can start changing the python code for 2 date columns.
3 points since it relies on coordination between multiple groups
Whiteboard: [points: 3]
The idea is to keep this spreadsheet as I shared the link with people - how about I add another date column and you sort by that one. I still don't understand the problem - if you take the order of the CSV right now you have the right order. I don't get why we should have to edit more just to work around a weird python bug?
Wow, I must be turning into a python programmer - I got all defensive when you called it a "bug" ;)

In any case, I've refactored the code since we spoke about this last, so it loops over the spreadsheet in the consistent order. I can change the query to order by 'id', but that makes too many assumptions, e.g., a single calendar processed in isolation from others; we already have other groups interested in doing their own spreadsheets.

If you add a date sort column that would be perfect.
I added a start and end date column to the spreadsheet - you can have a go on staging using that one.
I added a start and end date column to the spreadsheet - you can have a go on staging using that one.
Whiteboard: [points: 3] → p=3
Assignee: nobody → lcrouch
Jay, kicking this to you and/or Christian for review.

https://developer-stage9.mozilla.org/en-US/events

The Date column is standardized and all columns are sortable. Do we need to do anything else? 

I thought about an "End Date" column but it would add another column, and clutter up single-date events.

Do we want all columns sortable, or just a couple?
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Assignee: lcrouch → jay
My vote would be to make all columns sortable... it's just nice for users to be able to view the info any way they want.

It will be great to also do the sorting for the past events table below.

I also think it's important to display the end date column... since most of these events will be multi-day and that's an important bit of information for a lot of people to have.

If there is no end date, we can just use the start date or leave it blank.. not sure which is better practice.

Reopening so we can work out the remaining changes.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Jay: think I made all the changes. I say let's call it good for this release and let raymond do QA.
Assignee: jay → mozbugs.retornam
Status: REOPENED → RESOLVED
Closed: 13 years ago13 years ago
Keywords: qawanted
Resolution: --- → FIXED
Assignee: mozbugs.retornam → nobody
verified fixed https://developer.mozilla.org/en-US/events
Status: RESOLVED → VERIFIED
Whiteboard: p=3 → p=3 c=events
Version: MDN → unspecified
Component: Website → Landing pages
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.