- a daily tip on Twitter: @sfonplsql.
- videos on Practically Perfect PL/SQL and PL/SQL Channel
- resources at the Oracle PL/SQL page
- [well not me but....] Bryn Llewellyn's PL/SQL and EBR Blog
- weekly quizzes on the PL/SQL Challenge.
'Cause then I would feel bad that this post is about me asking you for something.
I am involved here at Oracle with both content generation (see above) and working on community-oriented apps that make it easier for you to access expertise and resources on Oracle Database developer-related topics, including:
As many of you are probably aware, content is great stuff ("Content is King"), but and especially for technology-related content, it can get "stale" - what is accurate today is misleading tomorrow; what is good advice today is a dead end tomorrow.
In addition, you need to have really good metadata about your content to make it easy for users to find what they need quickly (you say "Google", I say "Well, maybe, sometimes that's good enough...").
So I am working on a project to strengthen our content metadata and (eventually) engage our community to help us ensure that resources available to that community are as accurate and useful as possible.
To that end, I thought I would ask you:
- What metadata should we keep track of?
- What features could we, should we add to our community content applications/sites to improve their quality?
Current Ideas on Content Metadata
- Author: who produced the content
- URL of content
- Related to which product(s)?
- Which specific feature(s) within a product?
- Minimum version to which it applies
- Maximum version after which it no longer applies
- Expertise level (beginner, intermediate, advanced)
- Link to product documentation
What else can you think of?
What features could we, should we add to our community content applications/sites to improve their quality?
Thanks in advance for any spare brain cells you devote to this!