Details

    • Type: Improvement
    • Status: Deferred
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: Proposals for 2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Proposal:
      Hide

      I propose that we do two things:

      1) ascertain whether there are any strong in principal objections to implementing tagging
      2) if there are no strong objections organise an informal group of representatives to develop a suitable model

      Show
      I propose that we do two things: 1) ascertain whether there are any strong in principal objections to implementing tagging 2) if there are no strong objections organise an informal group of representatives to develop a suitable model
    • Resolution:
      Hide

      Deferred to 2.0 (5 March 2012)

      Show
      Deferred to 2.0 (5 March 2012)

      Description

      There have been repeated references to the possibility of implementing object/content tagging via one of the proposed new features (e.g. secondary types, or custom objects).

      I can imagine some requirements, including:

      • hierarchical tags
      • facility to relate a tag to an object (i.e. relationship, secondary type or something else)
      • query tags (e.g. top N tags by usage)
      • control security of tags
      • private versus public tags
      • specify some standard tags (e.g. 'My Favorites')
      • tag any object type (including custom objects if implemented)

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              david.churchland David Churchland (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated: