Hi Maxi,
I am saying that yes, you are right, it seems this file was not in 2.6 - it was added for the 2.7 release, along with a LOT of other changes (shown in the link I sent you) to how finding aids are managed.
For this reason, if you are going to do custom development for finding aid upload, I strongly encourage you to do it against the latest release, and not 2.6. When your institution wants to use your custom work, they will upgrade to the latest version you have developed against.
If you do your development based on the 2.6 release you are using currently, then when your organization wants to upgrade to 2.7 or later, your custom code will break (because as you can see, everything for finding aids changes between 2.6 and 2.7). Better to future proof it now and work on the latest version!
A quick overview of how we manage development branches in our AtoM GitHub code repository:
The latest version of the code is always in the
qa/2.x branch. This is our main development branch, and includes recently developed work that may or may not be tested yet. Generally, whatever is included here will be part of what is in the next major release (i.e. 2.5, 2.6, 2.7, 2.8, etc).
For each release, we create a stable branch, such as:
When we are preparing for a release, we create one of these branches for it. Only commits that have been tested and verified are added, so these branches are generally considered stable and ready for use by organizations in production. The first major release (for example, 2.7) as well as any minor releases for that version (2.7.1, 2.7.2, 2.7.3, etc) will be created from these stable branches.
The latest stable release of AtoM is version 2.7.3:
Unless we discover any security issues or major bugs we need to patch, the next release will likely be version 2.8. So: At this time, the stable/2.7.x branch includes everything in 2.7.3 but no more, while the qa/2.x branch includes everything in 2.7.3 and earlier, AND any additional work that has been done in preparation for the 2.8 release.
For these reasons, if you are doing new development it is wise to work with the latest code, so it will be ready for 2.8 (or at least 2.7!). Otherwise, the work will need to be redone when your organization wants to upgrade to a newer version.
Finally, some development resources for AtoM, in case you have not found them:
We have a number of resources on our wiki, here:
You can learn more about the Symfony 1.x PHP framework that AtoM was built with in their legacy documentation, here:
There are
slides that might be helpful, such as:
We also have entity relationship diagrams of AtoM's database schema on our wiki - you can see the latest version here:
Hope this helps!