Difference between revisions of "User talk:OmniMediaGroup"
| Line 71: | Line 71: | ||
What's really nice about ASK, as you've seen so far with your main listings, is that the recipes don't need to reside in any specific directories in order to pull them up into a summary report. That's the real essence of a flat structure - one that will come into play with the government roll-ups, as well as other large scale organizational projects. [[User:Snerfling|Snerfling]] 16:34, 20 January 2007 (PST) | What's really nice about ASK, as you've seen so far with your main listings, is that the recipes don't need to reside in any specific directories in order to pull them up into a summary report. That's the real essence of a flat structure - one that will come into play with the government roll-ups, as well as other large scale organizational projects. [[User:Snerfling|Snerfling]] 16:34, 20 January 2007 (PST) | ||
| + | |||
| + | : Sounds like you know my plan!! Working on the back end first and moving towards the front page. I may even venture into other areas of the Kitchen; remodeling, small appliances... | ||
Revision as of 00:42, 21 January 2007
Karen, Greg mentioned that you may be interested in some other MediaWiki extensions. Feel free to forward any recommendations/suggestions you may have.
What I'm particularly interested in is adding both Craigslist type classified advertising & eBay like auction marketing to Directory listings, along with the youTube extension.
You probably know where we're going with this - if you come across anything, could you let me know? Otherwise, I may have to cobble something together myself from scratch. Centiare 13:41, 11 December 2006 (PST)
Subsidiary listings
Karen, I've been talking to Greg about an easy way for you to create separate listings for your various blog properties, and then summarizing them at your primary Directory listing. You can see an example schedule at MyWikiBiz. We can go over a slightly more automated approach if you're interested. Centiare 13:38, 19 December 2006 (PST)
ASK
Example of others that have listed OMG as a friend:
<ask> OmniMediaGroup </ask>
This is exactly how one would create a query to list all subsidiaries of a given company, properties/websites/blogs controlled by an individual, papers/presentations given by an academic, etc.
Family on Centiare
Based on a conversation I had with Dad this morning, I think we're mere hours away from him opening an account on Centiare. Pretty amazing when a new Internet space utilizing the cutting edge in semantic technology can draw in a 73-year-old man whose most recent programming tasks were probably in COBOL. --Gkohs 08:58, 30 December 2006 (PST)
Semantic tags
Considering the (apparent) positive impact on Google SEO, I would recommend that you build into your various directory pages:
- Intra-Centiare wiki-links
- Semantic tags (even the State of Georgia "belongs" to Country:USA, you know?)
- Keep having fun, OMG. --MyWikiBiz 09:52, 9 January 2007 (PST)
- Karen, I went ahead and created the following four relations for the state listings. You can link through to each one, as well as the relation definition itself, which has a summary ASK query:
- I've updated your North Carolina listing for these 4 tags. I also created Attribute:Year Admitted as a replacement for Year Started. If you want, I can create four more attributes along the lines of city of, has city, has county, & county member of. Let me know. Centiare 12:26, 12 January 2007 (PST)
- I went ahead and created Relation:County Of, Relation:Has County, Relation:City Of & Relation:Has City. Note that cities only have to be listed under counties - an ASK query at the state level will list counties & their respective cities. See Directory:California for an example. Centiare 13:57, 12 January 2007 (PST)
- Thanks for all the new Attributes and Relations. The ASK query at state level is pretty slick!--OmniMediaGroup 14:05, 12 January 2007 (PST)
Attributes & Relations
Karen, I'm in the process of writing up guidelines for creating custom attributes & relations. Since I haven't completed it yet, I'll step in here real quick to provide a brief overview.
One thing I'm going to emphasize is the decision one must make between creating an attribute or relation for non-numeric values. That is, the logic is pretty clear about creating attributes for values like population, revenues, etc.
Where it can get a little fuzzy is if the value could be a relation (ie target page in which to create a relationship between articles). In this case, you can still choose to use an attribute, like CEO for a job title, BA for degree, etc, rather than a relation to main space articles that define/explain the meaning of those terms.
In the case of recipe_name, you start moving down the path closer to creating a relationship, especially if you anticipate creating stand-alone recipe pages in the future. Situations where relationships already work really well can be seen with the city->county->state->country roll-ups, etc.
Finally, there's the issue of ordinal identification ie situations where there may be multiple values OR associations between values, such as degree(s)<->year(s). Right now, relationships don't handle either very well (typically, they need an additional category identifier), but attributes are just the ticket. So even if something was logically a relationship, if you're going to have a complex data set, you may decide to use attributes instead. Centiare 09:11, 13 January 2007 (PST)
Main Space Articles
Karen, if you label an article 'recipe:apple pie', you're creating a Main space entry. That is, since there isn't a namespace 'recipe', the entry goes into the main space - the colon just happens to be part of the title.
Now, this isn't to say one can't use titles with colons in the Main space, nor is it saying that recipes don't belong in the Main space. It's just that anything in the mainspace needs to conform to NPOV + they can't be linked back to commercial directory listings unless they are approved by the Centiare:ERB.
What you may consider doing is creating a directory entry as a collection point for your recipes, then create them as subpages, along with relationships between each recipe and the page to which they relate. (Greg, do you want to take care of deleting/moving these entries?) Centiare 09:32, 13 January 2007 (PST)
- OK, I created Relation:Recipe Of & Relation:Has Recipe. All you have to do is create a collection point, then list each individual recipe with the 'Has Recipe' tag. Likewise, you can use the tag 'Recipe Of' within each individual recipe to associate it with its collection point.
- When in doubt, the Berlin<->Germany example is perfect for clarifying relationships: Capital Of and Has Capital. Almost all relationships can be structured in this type of subsidiary<->parent framework; that means all one has to do is think through which is which. I do it all the time - I write down Berlin-Germany on a piece of paper and then sketch out how new situations fit to this model. Centiare 09:47, 13 January 2007 (PST)
Relational Tags
Please see water cooler - news for info on the gov't rollup tags. I can help you follow the California example with the other 49 states if need be. Snerfling 12:38, 19 January 2007 (PST)
SubPages
OMG, your listings look great. At some point, you might want to consider creating add'l subpages to act like books/chapters. That way, you could organize the different recipe types & use the front page as a top-level lead-in/index.
What's really nice about ASK, as you've seen so far with your main listings, is that the recipes don't need to reside in any specific directories in order to pull them up into a summary report. That's the real essence of a flat structure - one that will come into play with the government roll-ups, as well as other large scale organizational projects. Snerfling 16:34, 20 January 2007 (PST)
- Sounds like you know my plan!! Working on the back end first and moving towards the front page. I may even venture into other areas of the Kitchen; remodeling, small appliances...
