Records Management
  1. Records Management
  2. RM-86

Custom Metadata: No way to delete once created

    Details

    • Type: Improvement Improvement
    • Status: Closed Closed
    • Priority: Critical Critical
    • Resolution: Won't Fix
    • Affects Version/s: 2.0
    • Fix Version/s: 2.2
    • Component/s: Custom Metadata
    • Labels:
      None

      Description

      I've entered this based on various comments made in the RM forum. I think this will cause trouble in a production environment. At the moment you can create custom metadata but there is no way to delete it, it cannot be done via the user interface not through editing the XML schema under the covers.

      There needs to be a way to delete a custom metadata field, although there are issues about doing this in a production environment, for example if that property is being used for access control, its far too easy to make a mistake (e.g. spelling mistake, wrong datatype) when creating custom metadata - and then there is no way to delete the mistake.

      Another approach to this might be to make the metadata property inactive, but doing this may then cause problems with duploicate property names.

        Issue Links

          Activity

          Hide
          Roy Wetherall added a comment -

          The Alfresco repository does not have the capability to allow reliable deletion of custom meta data.

          We will consider what (if any) work arounds can be put in place for RM 2.0

          Show
          Roy Wetherall added a comment - The Alfresco repository does not have the capability to allow reliable deletion of custom meta data. We will consider what (if any) work arounds can be put in place for RM 2.0
          Hide
          Alfresco QA Team added a comment -

          The issue is also actual for Alfresco Enterprise v4.0.1 (897), QALAB Stack 1 - RHEL 5.5 x64bit, MySQL 5.5, mysql-connector-java-5.1.17-bin.jar, Tomcat 6.0.35, JDK 6 U27 X64, Alfresco+ OpenLDAP 2.4.23, Clustering Schema 2; Client: FF 11.0, Windows XP SP3 x32bit
          ChristinaSh

          Show
          Alfresco QA Team added a comment - The issue is also actual for Alfresco Enterprise v4.0.1 (897), QALAB Stack 1 - RHEL 5.5 x64bit, MySQL 5.5, mysql-connector-java-5.1.17-bin.jar, Tomcat 6.0.35, JDK 6 U27 X64, Alfresco+ OpenLDAP 2.4.23, Clustering Schema 2; Client: FF 11.0, Windows XP SP3 x32bit ChristinaSh
          Hide
          Roy Wetherall added a comment -

          There is now way to fix this since the repository does not support this kind of model manipulation.

          Moving out to 2.1 fro consideration.

          Show
          Roy Wetherall added a comment - There is now way to fix this since the repository does not support this kind of model manipulation. Moving out to 2.1 fro consideration.
          Hide
          Ian Crew added a comment -

          Per http://docs.alfresco.com/3.4/topic/com.alfresco.Enterprise_3_4_0.doc/tasks/rm-custmeta-delete.html it is possible to delete custom metadata fields in RM, but I can't figure out how to actually do it. Is that documentation incorrect?

          Show
          Ian Crew added a comment - Per http://docs.alfresco.com/3.4/topic/com.alfresco.Enterprise_3_4_0.doc/tasks/rm-custmeta-delete.html it is possible to delete custom metadata fields in RM, but I can't figure out how to actually do it. Is that documentation incorrect?
          Hide
          Roy Wetherall added a comment -

          Marking this as won't fix for the time being since we can't do anything until repository support is added.

          Show
          Roy Wetherall added a comment - Marking this as won't fix for the time being since we can't do anything until repository support is added.

            People

            • Assignee:
              Closed Issues
              Reporter:
              Steve Rigby
            • Votes:
              2 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Date of First Response: