Uploaded image for project: 'Alfresco One Platform'
  1. Alfresco One Platform
  2. ACE-502

Transfer service : implement transferring of categories and tags

    Details

    • Type: Feature
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 5.0
    • Fix Version/s: 5.0
    • Component/s: Repository
    • Labels:
      None

      Description

      Steps to reproduce:

      1. Create any content @ source repo
      2. Allow content categorization and link it to any category (e.g. Tags)
      3. Transfer content to target repo and verify it's details

      Expected result

      Content should be linked to Tags category

      Actual result:

      Categorization is allowed for the content, however categorization info is discarded (content isn't linked to Tags category)

        Activity

        Hide
        mrogers Mark Rogers added a comment - - edited

        Issue confirmed as present in 3.3.

        The categorisation is implemented as a property called cm:categories that contains nodeRefs of the selected categories. These node refs won't exist on the target repository... The datadictionary type is d:category that is implemented as a NodeRef.

        On the destination after transfer the categories property is present but empty.

        <xfer:property name="

        {http://www.alfresco.org/model/content/1.0}

        categories">
        <xfer:values>
        <xfer:value className="org.alfresco.service.cmr.repository.NodeRef">workspace://SpacesStore/834eb228-7dd3-40f4-8a63-d3a9f8e8adc7</xfer:value>
        <xfer:value className="org.alfresco.service.cmr.repository.NodeRef">workspace://SpacesStore/30612ef3-296b-4400-a8c1-2054608325ac</xfer:value>
        </xfer:values>
        </xfer:property>

        Show
        mrogers Mark Rogers added a comment - - edited Issue confirmed as present in 3.3. The categorisation is implemented as a property called cm:categories that contains nodeRefs of the selected categories. These node refs won't exist on the target repository... The datadictionary type is d:category that is implemented as a NodeRef. On the destination after transfer the categories property is present but empty. <xfer:property name=" {http://www.alfresco.org/model/content/1.0} categories"> <xfer:values> <xfer:value className="org.alfresco.service.cmr.repository.NodeRef">workspace://SpacesStore/834eb228-7dd3-40f4-8a63-d3a9f8e8adc7</xfer:value> <xfer:value className="org.alfresco.service.cmr.repository.NodeRef">workspace://SpacesStore/30612ef3-296b-4400-a8c1-2054608325ac</xfer:value> </xfer:values> </xfer:property>
        Hide
        mrogers Mark Rogers added a comment -

        With a tag from share the property name is cm:taggable, but again it is of type d:category.

        Show
        mrogers Mark Rogers added a comment - With a tag from share the property name is cm:taggable, but again it is of type d:category.
        Hide
        mrogers Mark Rogers added a comment -

        Changing from bug to a task.

        Transfer of categories/tags is not yet implemented.

        Show
        mrogers Mark Rogers added a comment - Changing from bug to a task. Transfer of categories/tags is not yet implemented.
        Hide
        mrogers Mark Rogers added a comment -

        Please add to product backlog

        Show
        mrogers Mark Rogers added a comment - Please add to product backlog
        Hide
        amandaluniz Adei Mandaluniz added a comment -

        Any updates on this on the roadmap? It would be really useful

        Show
        amandaluniz Adei Mandaluniz added a comment - Any updates on this on the roadmap? It would be really useful
        Hide
        mfarman Mike Farman added a comment -

        We've not address this yet, but it would be useful to understand some more about your use case. Can you elaborate?

        Show
        mfarman Mike Farman added a comment - We've not address this yet, but it would be useful to understand some more about your use case. Can you elaborate?
        Hide
        amandaluniz Adei Mandaluniz added a comment -

        Basically our client has two Alfresco environments (Staging and Live).

        They're tagging/classifying content in Staging and replicating it to live to serve that content for their website. So their webscripts can perform searches using categories or tags. But, when replicating the content to live the categories and tags are not pushed.

        Show
        amandaluniz Adei Mandaluniz added a comment - Basically our client has two Alfresco environments (Staging and Live). They're tagging/classifying content in Staging and replicating it to live to serve that content for their website. So their webscripts can perform searches using categories or tags. But, when replicating the content to live the categories and tags are not pushed.
        Hide
        dward Dave Ward [X] (Inactive) added a comment -

        Is the QA expected result correct? I.e. is this a bug or enhancement request?

        Show
        dward Dave Ward [X] (Inactive) added a comment - Is the QA expected result correct? I.e. is this a bug or enhancement request?
        Hide
        alfrescoqa Alfresco QA Team added a comment -

        Successfully verified against Alfresco Enterprise v4.3.0 (PLATFORM1 r66165-b53) schema 7003, OOTB, RHEL 6.4x64; client: Win7x64, FF last.
        Transferred content is linked to the Tags category on the target repo.
        EugeneS

        Show
        alfrescoqa Alfresco QA Team added a comment - Successfully verified against Alfresco Enterprise v4.3.0 (PLATFORM1 r66165 -b53) schema 7003, OOTB, RHEL 6.4x64; client: Win7x64, FF last. Transferred content is linked to the Tags category on the target repo. EugeneS

          People

          • Assignee:
            closedissues Closed Issues
            Reporter:
            alfrescoqa Alfresco QA Team
          • Votes:
            4 Vote for this issue
            Watchers:
            9 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 0 minutes
              0m
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 1 day, 3 hours, 30 minutes
              1d 3h 30m