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. 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. Thinking of Oracle online documentation:
    - a link to the same information but for the current version (or all versions)

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

    ReplyDelete
  4. 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. Thanks, Babak. These categorizations are critical - and tough to get right. I like your "Change of Behavior" idea.

    ReplyDelete
  6. 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. Great point, Jeff, and a non-trivial issue in the world of APEX, from what I understand.

    ReplyDelete
  8. 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

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p

The differences between deterministic and result cache features

 EVERY once in a while, a developer gets in touch with a question like this: I am confused about the exact difference between deterministic and result_cache. Do they have different application use cases? I have used deterministic feature in many functions which retrieve data from some lookup tables. Is it essential to replace these 'deterministic' key words with 'result_cache'?  So I thought I'd write a post about the differences between these two features. But first, let's make sure we all understand what it means for a function to be  deterministic. From Wikipedia : In computer science, a deterministic algorithm is an algorithm which, given a particular input, will always produce the same output, with the underlying machine always passing through the same sequence of states.  Another way of putting this is that a deterministic subprogram (procedure or function) has no side-effects. If you pass a certain set of arguments for the parameters, you will always get

My two favorite APEX 5 features: Regional Display Selector and Cards

We (the over-sized development team for the PL/SQL Challenge - myself and my son, Eli) have been busy creating a new website on top of the PLCH platform (tables and packages): The Oracle Dev Gym! In a few short months (and just a part time involvement by yours truly), we have leveraged Oracle Application Express 5 to create what I think is an elegant, easy-to-use site that our users will absolutely love.  We plan to initially make the Dev Gym available only for current users of PL/SQL Challenge, so we can get feedback from our loyal user base. We will make the necessary adjustments and then offer it for general availability later this year. Anyway, more on that as the date approaches (the date being June 27, the APEX Open Mic Night at Kscope16 , where I will present it to a packed room of APEX experts). What I want to talk about today are two features of APEX that are making me so happy these days: Regional Display Selector and Cards. Regional Display Sel