"Tag" geodatabase items to filter what you see when you open the connection?

[AlfredBaldenweck]

This is kind of hard to articulate but.

I'm wondering if anyone knows a way to throw everything into a geodatabase, then only show tables that you designate as like, "active"?

For example, for one of my file systems, each project, as we get it, has the original files stored in a dated folder, and then the files are copied into a file geodatabase called "Active_Data". If a file comes in that is a newer version of something already in Active_Data, it overwrites it. For example, we've changed the project area several times. 

The reason I'm doing this is so that everyone doesn't have to worry about finding the latest copy of the project area; they just go to Active_Data, see "Project Area", and pull it in. If they need to find an earlier version, they can search the dated folders themselves.

Here's where I'm having trouble: What to do when the needs of the project change and suddenly we don't need that data in there anymore? Like if we were going to build a series of roads and then later determine that they aren't needed, I don't want to delete them out of that "Active" GDB, nor do I want to rename them, as both actions would break any links we had.

My current workflow is using a file gdb, but I imagine this would be more possible in an enterprise gdb?

I also don't think the solution here should be "group permissions", in the case of eGDBs, or the use of Layer files.

[MobiusSnake]

Back in the pre-Pro days there was a type of ArcObjects component called a Workspace Extension, it was a library you'd develop (usually a DLL made in C++ or C#) that you could apply to a geodatabase of any type to get certain types of custom behaviour out of that GDB.  These were similar to the more common Class Extensions that could be applied to tables and feature classes.  One type of custom behaviour that could be implemented was dynamically hiding certain datasets, for example based off naming conventions or a table that lists other tables that should be hidden - this was typically done so you could add your own system tables and hide them, the way the "GDB_" system tables are usually hidden from users.

To the best of my knowledge these don't exist in Pro, but I'm not very familiar with the Pro SDK, so maybe there's something similar?

[AlfredBaldenweck]

Interesting. I think this may be the modern equivalent? CIMWorkspaceConnection Class—ArcGIS Pro

Unfortunately, I know nothing about the Pro SDK, so I think it'll have to wait 😕