search

fcorti / alfresco-audit-analysis-reporting

A.A.A.R. migrated to Aflytics!
11 stars 11 forks source link

Data error when changing the type of a document #51

Open yregaieg opened 6 years ago

yregaieg commented 6 years ago

Following a type input error, I had to change a document type back to cm:content (form custom:document), I was able to do this on the alfresco side, without issues. AAAR extraction on the other hand did not catch the change and still shows the document in question as of the specific type (custom:content).

@fcorti, is this a bug or an intentional behavior ?

fcorti commented 6 years ago

So, we are talking about one document in particular. Are you extracting the custom:document type in AAAR? If yes, it should be extracted and updated. If not, the behaviour you describe is correct.

yregaieg commented 6 years ago

I am extracting both cm:content and custom:document. Obviously custom:document is a child type of cm:content

The user made an input mistake specifying a bunch of documents (6) as custom:document. And since the way back (from specific to more generic types) is not supported in Alfresco OOTB, I had to patch the node using some scripting. I just realized (6days after that) that I have no errors in the logs, and the documents in question did not change at all in datamart (they still carry the old modification timestamp). And I had to set them right manually in the DB to set things right, so I am guessing there is definitely something wrong with the extraction logic (unless going from specific to generic types is not supported in AAAR as well)

fcorti commented 6 years ago

Yes, under this scenario it should be extracted by the ETL. It's time for a debug. Let me know if I can help in debugging it.