Cloning Record Needs To Reference Full Arctos Record Guid, Not Just Catnum

by ADMIN 75 views

Understanding the Issue

When cloning a record using the Create Clone in Bulkloader function and specifying a relationship to another record, the cloned record only shows the "same individual as" relationship to the numeric catalog number in Identifiers in the bulkloader. This is because the identifier type is not set to Arctos Record GUID, and the identifier value only includes the numeric value for the catalog number, not the Darwin Core Triplet guid.

The Problem with Current Implementation

The current implementation of the Create Clone in Bulkloader function has a limitation that it does not set the identifier type to Arctos Record GUID when cloning a record with a relationship to another record. As a result, the cloned record only shows the numeric catalog number in the Identifiers section, without any information about the related item's GUID.

Request for Improvement

To address this issue, we request that the identifier type be set to Arctos Record GUID as default in this situation. Additionally, the identifier value should be the GUID of the related item, not just the catnum. This will ensure that the cloned record accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.

Example Use Case

To illustrate the issue, consider the following example:

The cloned record should be: https://www.dropbox.com/scl/fi/frxdo1688izmznwvgm8dr/Screenshot-2025-04-23-12.25.29.png?rlkey=ct4uwnh0f76np12392c3xqgms&dl=0

Benefits of Improvement

Implementing this improvement will have several benefits, including:

  • Accurate representation of data: The cloned record will accurately reflect the relationship to the original record, providing a complete and accurate representation of the data.
  • Improved data integrity: The identifier type will be set to Arctos Record GUID, ensuring that the data is consistent and accurate.
  • Enhanced user experience: Users will be able to easily identify the relationship between the cloned record and the original record, making it easier to work with the data.

Conclusion

In conclusion, the current implementation of the Create Clone in Bulkloader function has a limitation that it does not set the identifier type to Arctos Record GUID when cloning a record with a relationship to another record. We request that the identifier type be set to Arctos Record GUID as default in this situation, and the identifier value be the GUID of the related item, not just the catnum. This will ensure that the cloned record accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.

Recommendations

To implement this improvement, we recommend the following:

  • Update the Create Clone in Bulkloader function: Modify the function to set the identifier type to Arctos Record GUID when cloning a record with a relationship to another record.
  • Update the identifier value: Modify the identifier value to include the GUID of the related item, not just the catnum.
  • Test and validate: Test and validate the updated function to ensure that it accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.

Q: What is the current issue with cloning records in Bulkloader?

A: When cloning a record using the Create Clone in Bulkloader function and specifying a relationship to another record, the cloned record only shows the "same individual as" relationship to the numeric catalog number in Identifiers in the bulkloader. This is because the identifier type is not set to Arctos Record GUID, and the identifier value only includes the numeric value for the catalog number, not the Darwin Core Triplet guid.

Q: What is the problem with the current implementation?

A: The current implementation of the Create Clone in Bulkloader function has a limitation that it does not set the identifier type to Arctos Record GUID when cloning a record with a relationship to another record. As a result, the cloned record only shows the numeric catalog number in the Identifiers section, without any information about the related item's GUID.

Q: What is the requested improvement?

A: We request that the identifier type be set to Arctos Record GUID as default in this situation. Additionally, the identifier value should be the GUID of the related item, not just the catnum. This will ensure that the cloned record accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.

Q: What are the benefits of implementing this improvement?

A: Implementing this improvement will have several benefits, including:

  • Accurate representation of data: The cloned record will accurately reflect the relationship to the original record, providing a complete and accurate representation of the data.
  • Improved data integrity: The identifier type will be set to Arctos Record GUID, ensuring that the data is consistent and accurate.
  • Enhanced user experience: Users will be able to easily identify the relationship between the cloned record and the original record, making it easier to work with the data.

Q: How can this improvement be implemented?

A: To implement this improvement, we recommend the following:

  • Update the Create Clone in Bulkloader function: Modify the function to set the identifier type to Arctos Record GUID when cloning a record with a relationship to another record.
  • Update the identifier value: Modify the identifier value to include the GUID of the related item, not just the catnum.
  • Test and validate: Test and validate the updated function to ensure that it accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.

Q: What are the next steps?

A: We recommend that the development team update the Create Clone in Bulkloader function to set the identifier type to Arctos Record GUID and update the identifier value to include the GUID of the related item. Once the update is complete, we recommend testing and validating the function to ensure that it accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.

Q: Who should be involved in implementing this improvement?

A: We recommend that the following individuals be involved in implementing this improvement:

  • Development team: The development team should update the Create Clone in Bulkloader function to set the identifier type to Arctos Record GUID and update the identifier value to include the GUID of the related item.
  • Quality assurance team: The quality assurance team should test and validate the updated function to ensure that it accurately reflects the relationship to the original record and provides a complete and accurate representation of the data.
  • Project manager: The project manager should oversee the implementation of this improvement and ensure that it is completed on time and within budget.

Q: What are the expected outcomes of implementing this improvement?

A: We expect that implementing this improvement will result in:

  • Accurate representation of data: The cloned record will accurately reflect the relationship to the original record, providing a complete and accurate representation of the data.
  • Improved data integrity: The identifier type will be set to Arctos Record GUID, ensuring that the data is consistent and accurate.
  • Enhanced user experience: Users will be able to easily identify the relationship between the cloned record and the original record, making it easier to work with the data.