Status Reports as Feature Services for Enterprise and ArcGIS Online

[LuskClint]

I manage both the Enterprise and ArcGIS Online Portals for my City with around 1000 total users.  One of my most used tools is the Member Reports, Item Reports, and Credit Reports from the Status Page in both my portals.  I export those reports almost daily and run them through an FME process to combine them with other city reports, just so I can turn that data back into a feature service and plug it into a couple of different dashboards.  

In those dashboards I'm tracking who's completed what training, who owns the most old content that should be deprecated/deleted, who belongs to what department, who their boss is, and even who's been inactive for so long their account should be disabled.  

It would make my life much easier, if instead of having to schedule, then manually download the report .CSVs if they were just accessible as a feature service.

I attached a screen shot to help illustrate the sort of things I'm doing with the data.

[George_Thompson]

Have you seen this blog?: https://www.esri.com/arcgis-blog/products/arcgis-online/administration/managing-arcgis-online-conten...

It provides some of the functionality that you are requesting, and you could expand it to meet some more of your needs.

[LuskClint]

Thanks @George_Thompson , that is helpful.  I'll have to see if I can force that to work with our Enterprise as well.  It looks like it's providing the same-ish information as the status reports... I just wish there were less steps involved.  Keeping a notebook running to then go through my data transformation and dashboard process is just one more complicated step that could be avoided if that same data was just already available as a feature service.

[dgiersz_cuyahoga]

I think what @George_Thompson is getting at is that most, if not all, of your workflow steps can be done via Python.  You could then set the python script (in this example, an ArcGIS Notebook) to run on a schedule and it would update the data for you.

[LuskClint]

So for anyone else following this issue, I set up an ran the notebooks to see how they compared.

Here is what I learned.  The reports are similar... but not quite the same as the status report exports.  Mainly you're missing the attachment file size... which I get is probably a pain.

This is a standard notebook, so it's not costing me credits to run (I'm pretty sure at least).  So it's a step in the right direction... but I still wish I just had all the existing status reports as built in feature services.  Again, it'd be one less thing to set up, and my experience with python makes me think this code will break at some point soon anyways.

But it's something.  I'll have to try it in my enterprise when I get a chance as I've only ran this in AGOL so far.