Latest Contributions by HilaryCampbell

Zachary, FYI I've created an idea for this:  https://community.esri.com/ideas/19259  Feel free to vote it up and spread the word so others do too.  Thanks!    ... View more

So, is XML the only method for extracting schemas in Pro?  I have no experience with XML.  The Extract Data tool in the Distributed Geodatabase toolbar in ArcMap was seamless and simple:  you could select the Schema only option and the result was a fully set-up GDB shell with no data in it, without exporting or importing anything.  This is ideal for documentation, testing, etc.  If there is no plan to replace the Extract Data tool in Pro, please advise ASAP.   This affects a number of my current projects.  Thanks. ... View more

Hi, Robert.  Sorry, I haven't been on here consistently in the last couple of months.  No, I'm not able to upgrade to 2.5 yet.   ... View more

Hi, Bret.  How are you making out with this? I work on the GIS team in our IT department, and we support business units throughout the organization (municipal government), which has been in this process for over 5 years now, and we still don't have it all figured out.  However, we have arrived at a few conclusions which might be useful to you: Defining Core Principles: Data is a Corporate Asset Data is Accessible Data is Accurate Data is Secure Defining Roles:  This was a key to "selling" data governance in general, and a centralized Asset Registry in particular, to senior management.  Every dataset or group of datasets has three roles assigned to it:  a Strategic Data Steward (SDS), Operational Data Steward (ODS) and Data Custodian (DC).  The SDS is a senior manager within the relevant department, such as Parks & Recreation or Public Works, and is responsible for data governance outcomes - accountable for the quality and integrity of the data..  The ODS is a data analyst with the IT group who works with the SDS to carry out data governance operations for that department such as database design and analysis, as well as  providing oversight and expertise, and performing QC/QA tasks on the data.  The DC is the hands-on data editor who is responsible for updating and maintaining the data itself, and works for the relevant department.  We are building spatial data expertise throughout the organization with this approach, rather than having one centralized group manage all spatial information.  This also ensures that the person(s) managing the data possess the first-hand knowledge needed for it. Managing a Corporate Asset Inventory: A decision was made to store all asset information in our corporate GIS (SDE, now ArcGIS Enterprise).  This required an organization-wide view of the data: introducing the idea that the GIS is managing data for the entire organization, not just for one specific use or group.  We are working towards making the GIS the authoritative source of truth for all asset information.  This transition is still in progress for us, but it is a significant corporate culture change which takes time. Defining Corporate Best Practices: Beyond what I've mentioned previously, it was essential to: create clear asset definitions for each asset type (e.g., Guide Rail - A barrier system designed to keep people or vehicles from straying into dangerous areas.) limit the number of data editors for each asset type, to improve data consistency and build expertise define data standards and practices that meet business requirements (spatial accuracy, critical data attributes, etc.) audit data quality Note that the actual activity of adding, changing or removing records is a separate process and not part of the data governance plan as such.  Data governance would determine who would perform these tasks. I hope this is of some assistance to you.  Cheers. ... View more

SQL cannot be used to filter versioned databases. From the error link above: "Currently, only feature services support SQL expressions. For other formats, use Python or Arcade expression types." ... View more

Hi, Kory.  Thank you for the error reference.  Question:  will full SQL functionality be restored in ArcGIS Pro, or is it being deliberately phased out?  I for one have built up a lot of expertise in SQL over the years. ... View more

We're moving to ArcPro later this year, but the loss of Diagrammer will be a big problem.  Any updates on this? ... View more

As much as I appreciate your input, Kevin… and I’m sure we’ll be incorporating your code in some of our apps… Stuart is right. This is core functionality which should be available out of the box, not a function we have to customize. ... View more

This issue has been around for quite a while now.  I spoke about this with Kelly Gerrow at the AGOL island at the UC last week.  We talked about what types of users could be automatically deleted, as well as what could happen with user accounts which are automatically disabled on a specified date, instead of deleted. I suggested that users who did not create any content in their accounts (our org has a lot of read-only viewers) could be deleted outright. User accounts which do have content could be disabled, which would allow the account administrator(s) the opportunity to move that content to another location before removing the user from the account. Either option should free up the use of that identity. For organizations with a finite number of named user identities in high demand with frequent turnover, the disable option would be very attractive: the quota of named user identities assigned to an account should not be impacted by disabled identities. Making administrators responsible for checking who is doing what and who is finished when is not optimal. There has to be a better way. Whether for student placements or term contracts, projects or short-term initiatives, AGOL administrators need the ability to set an expiry date on accounts. I’d also like to suggest that identities are frequently assigned to people who never use them, in anticipation of a perceived need which is never realized. The administrator should have the ability to set warnings for unused identities, with an option to send users system-generated notice that their accounts will be disabled if the account is inactive for a defined period of time (e.g. 90 days).  Admins would also need an easy way to find/filter on disabled accounts and accounts nearing expiry.  I love Mōno Simeone's idea of tying an expiry date to a role. bulk administration‌  expiry date‌ ArcGIS-Online‌ #named users‌ #AGOL_identities‌ ... View more

Hello, KC.  May users submit more than one abstract for consideration?  We have a number of initiatives underway in our organization, each with a distinct focus or purpose.  As long as each submission is unique, is it acceptable for the same user to submit multiple abstracts? I'd also love an extension on the deadline.  🙂 ... View more