Does anyone have an answer as to how the GPT does the following:
1. Matches a user-uploaded record with a pre-existing one? E.g., what is the criteria used for determining when a user uploads a new record vs overwriting an existing one? We have some users (such as myself) who can upload a record to the GPT, then reupload it and overwrite the existing one, whereas others, under the exact same conditions, are never able to overwrite an existing record. We???ve performed a number of tests and have never been able to create a scenario where the user with the problem can overwrite the pre-existing record. This happens even if the user uploads a record, downloads the newly uploaded record, then re-uploads it without any changes. S/he always contributes a new record to the GPT as opposed to overwriting the existing one. This is causing problems for a number of reasons: 1. We???d like to point to UUIDs from other web pages; 2. Access levels need to be reset for new records; 3. Approvals need to be performed for new records. Because of these three issues (most importantly the UUIDs being maintained), we are at a standstill with some users who would like to point to specific records at our portal. As such, we???re not sure we understand the rules for overwriting an existing record at the GDG and would like to know if anyone has had similar problems or knows the answer.
2. Maintains UUIDs for records? In prior versions of the software, when a user downloaded a record from GPT, the software would insert a tag into the record that recorded the UUID (e.g., <Esri><PublishedDocID>{4A2F897E-E1E4-453E-9A29-674A520E4B94}</PublishedDocID></Esri>) This tag would then also be consistent with one???s records at GOS if one were to upload this record to GOS. Now it seems that this element is not being written to the output record and we are having trouble maintaining UUIDs for our contributors who upload content to the GPT. We???ve tried to manually insert this UUID into the output record (using the format shown above), but the GPT does not seem to recognize this tag. We could live with the manual insertion method if it were viable now, but it doesn???t seem to work. This does still work at GOS. As such, we???re not sure how the UUIDs are being maintained. Input is welcome.
