Skip to main content

Content Management for Oracle Database Developers - what do you need?

Yes, yes, I know: another post with little or nothing to do with PL/SQL. My apologies. But remember, I do offer
So please don't say "But what have you done for me lately?" :-)

'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?

Additional Features?

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!

Steven

Comments

  1. astramieriNovember 13, 2015 at 12:03 AM

    Just a few more ideas for content metadata:
    1) estimated time required to read/listen/make-practice
    2) rating system (e.g. 1-5 stars)
    Cheers
    A.

    ReplyDelete
  2. Sabine HeimsathNovember 13, 2015 at 3:41 AM

    Thinking of Oracle online documentation:
    - a link to the same information but for the current version (or all versions)

    ReplyDelete
  3. Steven FeuersteinNovember 13, 2015 at 6:12 AM

    @A, yes great points, thanks!
    @Sabine: yes, multiple versions are important.

    ReplyDelete
  4. Babak TouraniNovember 14, 2015 at 12:15 PM

    Perhaps categorizing content in terms of things like "Performance", "Style Guide", "Instrumentation", "Change of Behaviour" (e.g. NO_DATA_NEEDED and how it's treated differently between 11.2.0.3 and 11.2.0.4),... I know, you might need an Ontology expert to put all these and similar phrases under one "category" but I believe having such metadata would help.

    ReplyDelete
  5. Steven FeuersteinNovember 16, 2015 at 7:48 AM

    Thanks, Babak. These categorizations are critical - and tough to get right. I like your "Change of Behavior" idea.

    ReplyDelete
  6. Jeffrey KempNovember 17, 2015 at 12:14 AM

    To be honest, I think the makers of StackOverflow have the right idea here: making sure that all content is Google-friendly is the most scaleable way of ensuring content is easily discoverable.

    ReplyDelete
  7. Steven FeuersteinNovember 17, 2015 at 2:50 AM

    Great point, Jeff, and a non-trivial issue in the world of APEX, from what I understand.

    ReplyDelete
  8. Scott SwankNovember 17, 2015 at 8:49 AM

    I would step back from the idea of Oracle content to that of a content repository. There's a decent Java spec https://jcp.org/aboutJava/communityprocess/final/jsr170/index.html. Things to consider include: content-type/mime-type, namespace, versioning, full-text search, hierarchical (directory-like) storage, hierarchical search (xpath?), fine-grained access, authorship and collaboration, listening-to/observation-of content with change notification.

    I don't mean to include everything in version 1.0 (or 0.3?), but rather to aim for a general-purpose content repository, implementing relevant features as needed/useful.

    ReplyDelete

Post a Comment

Popular posts from this blog

Running out of PGA memory with MULTISET ops? Watch out for DISTINCT!

A PL/SQL team inside Oracle made excellent use of nested tables and MULTISET operators in SQL, blending data in tables with procedurally-generated datasets (nested tables).  All was going well when they hit the dreaded: ORA-04030: out of process memory when trying to allocate 2032 bytes  They asked for my help.  The error occurred on this SELECT: SELECT  *    FROM header_tab trx    WHERE (generated_ntab1 SUBMULTISET OF trx.column_ntab)       AND ((trx.column_ntab MULTISET             EXCEPT DISTINCT generated_ntab2) IS EMPTY) The problem is clearly related to the use of those nested tables. Now, there was clearly sufficient PGA for the nested tables themselves. So the problem was in executing the MULTISET-related functionality. We talked for a bit about dropping the use of nested tables and instead doing everything in SQL, to avoid the PGA error. That would, however require lots of wo...
4 comments
Read more

How to Pick the Limit for BULK COLLECT

This question rolled into my In Box today: In the case of using the LIMIT clause of BULK COLLECT, how do we decide what value to use for the limit? First I give the quick answer, then I provide support for that answer Quick Answer Start with 100. That's the default (and only) setting for cursor FOR loop optimizations. It offers a sweet spot of improved performance over row-by-row and not-too-much PGA memory consumption. Test to see if that's fast enough (likely will be for many cases). If not, try higher values until you reach the performance level you need - and you are not consuming too much PGA memory.  Don't hard-code the limit value: make it a parameter to your subprogram or a constant in a package specification. Don't put anything in the collection you don't need. [from Giulio Dottorini] Remember: each session that runs this code will use that amount of memory. Background When you use BULK COLLECT, you retrieve more than row with each fetch, ...
4 comments
Read more

PL/SQL 101: Three ways to get error message/stack in PL/SQL

The PL/SQL Challenge quiz for 10 September - 16 September 2016 explored the different ways you can obtain the error message / stack in PL/SQL. Note: an error stack is a sequence of multiple error messages that can occur when an exception is propagated and re-raised through several layers of nested blocks. The three ways are: SQLERRM - The original, traditional and (oddly enough) not currently recommended function to get the current error message. Not recommended because the next two options avoid a problem which you are unlikely  to run into: the error stack will be truncated at 512 bytes, and you might lose some error information. DBMS_UTILITY.FORMAT_ERROR_STACK - Returns the error message / stack, and will not truncate your string like SQLERRM will. UTL_CALL_STACK API - Added in Oracle Database 12c, the UTL_CALL_STACK package offers a comprehensive API into the execution call stack, the error stack and the error backtrace.  Note: check out this LiveSQL script if...
5 comments
Read more