Admin:Index

From The Scuba Wiki

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: Users.
• This page has been locked to prevent editing.

You can view and copy the source of this page:

== Admin Index Page == :[[Admin:Categories]] ---- :[[Admin:Creating_Event]] - Deleted intentionally. Add An Event page is working for the most part (see below) :[[Admin:Calendar]] ---- :[[Admin:Maps]] :[[Admin:Dive Sites]] :[[Palancar Gardens]] :[[Las Palmas]] == <font color="green">Thoughts and To-Do List</font> == === Calendar === * <del>Data points for calendar items</del> ** <del>Date(s) (multiple entry field)</del> ** Time(s) *** <del><font color="red">Ok. Problem here. On a multi day event, the times may differ on days. Need to find a way to associate the times with the particular day.</font></del> **** <del><font color="blue">In thinking about this last night, the intent with the calendar is to show the dates of the events, not create a scheduling app. I'm going to do some research on how difficult it would be to create the time association per day, but I'm leaning torwards time not being a parameter.</font></del> **** <del><font color="red">Ok. Date is a valid property type, time is not. Time is supported through the date type, but the default data entry formats for a date type are based on day/month/year, not time. This include the YUI control. Given the challenges, I think that (for the time being), time will not be included as a parameter.</font></del> **** Had a brainstorm last night and tested it this morning. Was able to associate a text field to the specific date field that can show the times for that day. Won't be a part of any queries, but will display on the event itself. ** <del>Cost</del> ** <del>Address (for proximity searching)</del> *** <del>Split into multiple fields, Address1, Address2, Address3, City, State, Post Code (Zip), Country</del> *** <del>Concatenated and geocoded for mapping purposes, see [[Template:Event]] for details</del> ** <del>Phone number</del> ** <del>External Link(s) - show or sponsoring LDS (multiple entry field)</del> ** <del>Diving/Non-Diving</del> ** <del>Training Agency (multiple entry field)</del> *** <del>Property exists, but I'm not sure how relevant this is. Am removing it from the form for now, so it can't be data-entered.</del> ** Event Type (These should probably be categories) *** Needs sub-sections to be developed *** Travel Expo *** Gear demo *** Training (should this be used for LDS lake weekends?) - Make the category the LDS name. *** Dive Trip *** ??? ** Description (main wiki) * <del>Template for calendar items - <font color=blue>Multi-day form has been created, a lot more work to do but it is now adding in an event on multiple days properly.</font></del> * There are 3 templates for right now: [[Template:Event]], [[Template:Event_link]], [[Template:Event_date]] ** [[Template:Event]] and [[Template:Event_link]] I think are done for the time being. I like how they look, although the [[Template:Event_link|Link]] template could be tweaked to list the link(s) at the bottom of the page, instead of how it displays directly under the last link of the Wiki text. Need to look at how to do that one... Low priority. ** Also the Address could be tweaked just a bit. The state field is kind of pushed out, but not worried about that right now. ** [[Template:Event_date]] needs work. It enters dates ok, but I don't like how they're displaying currently. <font color="blue">Next on the agenda.</font> * Need to start looking at building the user interfaces. Especially the ability to pull "local" events... === Semantic/MediaWiki === * Maps (and calendars) will display up to 10000 items from a single query (query has to be built that way).<font color="red"> But... this makes for a very long page load time, so the defaults should probably be left in place.</font> * More user friendly method of querying * Other data points we want to capture for other subjects? ** For user information: http://www.mediawiki.org/wiki/Extension:SemanticSignup * Need to install ParserFunctions extension, unless it already is. * Caching has been turned off temporarily. See http://meta.wikimedia.org/wiki/MediaWiki_FAQ#How_do_I_completely_disable_caching.3F === Dive Shops === * Data points * Template === Graphics/logos/skins === * I like the standard wikipedia skin, although we could look at options. Look at wikipedia and see what skins are available. If others are, then it should be assumed that users must be using them, and we'd want to offer the same abilities * Need to work up some logo concepts - I like a wireframe earth, with a dive flag in the background, and maybe a few pins showing dive sites??? Maybe a rotating earth and/or waving flag??? Don't want to get too large a file, though. * Could a flash document be inserted as the logo? Could handle the above concept with a smaller file size <font color=blue>If at all possible I'd stay away from flash</font> * Slogans for the site? ** The Scuba Wiki - Share Your Sport ** The Scuba Wiki - Knowledge is Power ** Other ideas? === DB Stuff === [[admin:db|DB Stuff]] === Rating System === * Look at http://discoursedb.org/wiki/Special:AddData/Item/Example_item for an example of adding templates multiple times to a form. === Dive Sites === '''<font color="purple">are fully developed (at least for the time being...)</font>''' * Should we make GPS coordinates a mandatory entry on the form for adding a Dive Site? <font color="blue">I would think this would discourage entering of new dive sites, maybe some sort of obnoxious message at the top that the site needs a GPS link?</font> <font color="green">Yea, but if it doesn't have a GPS point it won't show on a map... But having an entry that needs to be completed may be worthwhile from an informational standpoint. I don't know...</font> * Need to redo temps from avg to a summer avg and a winter avg. <font color="red">- Done ** Now have a summer temp and winter temp</font> * I don't like the avg depth property anymore. At least as the only point. re: Wrecks. Need to come up with a new plan. Something like depth of shallowest attraction/deepest attraction. Want to give this more thought before making any changes. <font color="red">- Done ** Now have a top depth and bottom depth and changed description to Average depth range.</font> * Need to come up with a standard template for information we want to capture on dive sites (non-queryable). A format like history, attractions, external sites, etc. * Should current be changed to current/surge, or should there be a separate data point for surge? Ocean shore diving can definitely have this. It can impact diving, making it challenging for novice divers, and is not the same as current. <font color="red">- Done ** Changed description to current/surge, but property is still Site_current. May change property name, undecided.</font> [[File:World.svg|width=600]] == <font color="red">Deprecated</font> == :[[Admin:Test]] :[[TestSMW]]

Return to Admin:Index.