- It depends.
- Yes, you can add a field.
- Yes, you can modify the cause field using SQL Developer (not ArcCatalog)
- Considering the role Archive plays for Responder: Yes, you can probably edit the data in the Archive tables outside of the application but it is NOT recommended. You better have a VERY good understanding of what you are changing and what role it plays with the other Archive tables. Change the wrong thing and Archive Explorer may behave very strangely and your reporting stops working because it doesn't understand the data in the tables.
- You can add a field pretty easily to the Archive schema, but you won't be able to edit or view it through Archive Explorer. It would only be editable/viewable through SQL Developer, a custom app, or through a customization of Archive Explorer.
- You can modify the cause field with SQL Developer, but not ArcCatalog or ArcMap. This is because the Archive tables are not typically registered with SDE, which makes editing them with Arc products impossible. You'll know if they are registered with SDE if they have the auto-numbered ObjectID field as an attribute. And if you do modify the cause field with SQL Developer, make sure the value you're changing to exists in the ArchiveSchemaConfig.XML as a valid domain value.
Someone from Tech Support can correct me if I'm wrong here...
Yes you can modify and add a custom field but it depends on what you are trying to do here. Custom triggers on the tables can cause problems though with us trying to insert or update records through the software.
As for the cause codes, we run reports on them and do exclude some cause codes. Changing them outside of Responder also prevents us from tracking who made the change.