Talk:Design Document

From Species File Help
(Difference between revisions)
Jump to: navigation, search
(Deleted sections,cleaned up others --~~~~)
 
Line 1: Line 1:
  
  
 +
Some MediaWiki concepts, and/or special pages needing extra consideration IMHO due to their need for naming conventions, potential for ambiguity and disagreement, and their visible nature as entry points: '''portals'''; '''overview pages'''; '''categories'''; '''contents'''.
  
−
I like the idea of trying to emulate Wikipedia and their organization to a large extent. So for example, the main page provides an easy access point, while providing simple access to higher level categories and the table of contents. A possible combination of higher level natural categories for drilling down (editing, programming, administration) are on the main design document page. Having access to data typically organized by wikis such as lists and categories forms a higher level category in Wikipedia.
+
If and when whatever top categories are established, it seems that overview sections and/or portals then provide a general introduction to the main subcategories and other areas covered. Probably best if some sort of consensus established before somebody decides to just do it. Then again... Also, I deleted earlier section from SFS website...--[[User:Maehr|MikeMaehr]] 14:38, 6 April 2012 (CDT)
−
 
+
−
I think things like the logging in page just created should somehow be made prominent, easy to find, possibly in an "overview" page or something a la Wikipedia.
+
−
 
+
−
If and when whatever top categories are established, it seems that 'overview' sections then provide a general introduction to the main subcategories and other areas covered. For example, the SF website welcome page seems like it has much that could simply be transferred into sections of the wiki. The following example is from SFS site [http://software.speciesfile.org/HomePage.aspx]:
+
−
 
+
−
----
+
−
 
+
−
The database is a SQL Server application.  The Species File Group (SFG) has developed an SFS template that contains the basic database table structure as well as the stored procedures, user-defined functions and views used by species files.  The template is used as the starting point for new species file databases.
+
−
 
+
−
The website is a Visual Studio application. It provides the interface between the database and those who use it. The website provides not only the interface used by the public, but also the much larger interface used by the editors who manage the data contained in the database. A template has also been prepared as the starting point for new species file websites.
+
−
 
+
−
Species File Software includes three sets of source code:
+
−
 
+
−
*File specific code.  The information contained in this section is unique to the taxonomic group and is under control of its custodian.
+
−
*Common code.  This software is common to all species files.  It is under control of the Species File Group at the Illinois Natural History Survey.
+
−
*Database application code.  This code is contained within the database.  It enables more efficient execution than would be possible if the common code were limited to queries as the only interface to the database.
+
−
 
+
−
----
+
−
 
+
−
To me these are good starts to pages...
+
−
 
+
−
----
+
  
 
Category lists looks like a great start.  I'd keep as separate categories, and think about highlighting in general, the import and export of data.  What's "Data source"? --[[User:MattYoder|MattYoder]] 08:06, 30 March 2012 (CDT)
 
Category lists looks like a great start.  I'd keep as separate categories, and think about highlighting in general, the import and export of data.  What's "Data source"? --[[User:MattYoder|MattYoder]] 08:06, 30 March 2012 (CDT)
 +
"Data Source" within a SF has its own ID, is searchable and mostly just used in cases where reference not considered appropriate, e.g. if I uploads some of my own sounds or images or other data. --[[User:Maehr|MikeMaehr]] 14:38, 6 April 2012 (CDT)

Latest revision as of 14:38, 6 April 2012


Some MediaWiki concepts, and/or special pages needing extra consideration IMHO due to their need for naming conventions, potential for ambiguity and disagreement, and their visible nature as entry points: portals; overview pages; categories; contents.

If and when whatever top categories are established, it seems that overview sections and/or portals then provide a general introduction to the main subcategories and other areas covered. Probably best if some sort of consensus established before somebody decides to just do it. Then again... Also, I deleted earlier section from SFS website...--MikeMaehr 14:38, 6 April 2012 (CDT)

Category lists looks like a great start. I'd keep as separate categories, and think about highlighting in general, the import and export of data. What's "Data source"? --MattYoder 08:06, 30 March 2012 (CDT) "Data Source" within a SF has its own ID, is searchable and mostly just used in cases where reference not considered appropriate, e.g. if I uploads some of my own sounds or images or other data. --MikeMaehr 14:38, 6 April 2012 (CDT)

Retrieved from "http://help.speciesfile.org/index.php?title=Talk:Design_Document&oldid=166"
Personal tools
Namespaces

Variants
Actions
Navigation
Species Files
Wiki
Toolbox