Hi @HeatherC and others–
I’ve added a guide specifically covering all there is about Deaccessions today in response to community requests:
Paul’s method of defining a pick list for export filtering or searching is currently the most effective strategy I can think of. At this time, there is no ‘flag’ field indicating that a particular object has been deaccessioned. This is mainly because deaccessions are not directly linked to Collection Objects but rather to Preparations associated with an object.
I don’t believe there is a reliable way to exclude an object based on its relationship to a preparation if it has been deaccessioned. Therefore, indicating this via the Collection Object with a flag is something I recommend.
For instance, if you are exporting preparations using the GGBN Preparation Extension, you could exclude preparations that are unavailable due to being linked to a deaccession-adjacent interaction. You can do this by adding an additional filter to the query that excludes those linked to deaccession through any interaction.
If anyone has suggestions on the best approach, please let me know! Perhaps a virtual field that indicates whether any portion of material is deaccessioned, or a field that automatically flags if all preparations have been deaccessioned, would be necessary.