I am trying to clean up items in my AGOL, but it is super hard as I can not tell *exactly* which maps/layers are being consumed and which are not. When you go into a web map, you can see what layers and base maps are being used (pic below) and go to the feature classes there.
I would really like to see this implemented on other things.
For example, if I have a feature layer I would like to be able to view the item details page (the usage tab could be a great place for this!) and see which web maps are consuming it.
An example may be: PointLayer (lets say this is trees). If I go to the usage tab, I can see that this tree layer is being consumed by Map A, Map B and Map C.
This way, you could quickly tell which layers/maps are not being consumed by anything else, especially if they were made in the short term.
I feel like this could also go for web apps, as the 'usage' tab could bring you back to the web map, which brings you back to the layers being referenced.
I know some of this may be able to be avoided with better organization. However, I often find myself remaking layers for different purposes (i.e. a boundary with a fade, a boundary without a fade). Later, if I want to replace those, it is super time consuming to click through EVERY map/app just to figure out what all needs replacing.
Thanks 😊
There are a lot of ideas relating to the same thing. I agree that it would be amazing if we could have this list. I would look at older ideas and up vote those.
I think this might already be coming. In the ArcGIS Online Roadmap at this year's UC, there were slides on Dependencies and Item Usage, and a general framework to make it easier to find out how items are related to each other seems to be in progress. I'm currently using Python to crawl through everything as a workaround, and what they showed look MUCH easier.
I came here to say this, so in full support, I will just paste the text I wrote about it:
Each item in ESRI online storage needs a family tree--a graphic that shows what other items it is linked to. It took me quite a while to figure out where the problem in the permissions was located for a two layers, embedded in a web map, which was embedded in an instant app that is embedded in a StoryMap. A graphical phylogeny would solve that problem.
It does not even need to be graphical--that might be overdesign and take too much processing power or programming time. It could just be a list of linked items, with sharing permissions choices enabled right inside the list. If the person trying to change the permissions of an item is not the owner, then the list should provide a canned email to send to the person who can change the permissions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.