ramonski on state-menu-titles
Changelog updated (compare)
I am moving test server DB to live server and I want to remove/delete all the test data like "AnalysisRequests" etc. but not master data like SampleTypes, AnalysisService etc.
How I can achieve this ?
I know there is security enhancement implemented in latest release of senaite.core that even admin can't delete the objects.
But there is a scenario in which as stated in quoted caption I want to know that how it can be achieved. I think there should be a mechanism to achieve this. If i want to allow "admin" to delete ARs, what code changes may require ? where I need to tinker the code ?
I also want to reset ID for ARs after deleting ARs from ID-server functionality. How it is possible?
bin/instance debug). Both variants require in depth knowledge of the Code and the architecture of the content objects.
Thanks @xispa for your detailed view about the functionality. My intention to provided such facility was through ZMI which is accesible by Plone Admin only not by ordinary users. Because, through ZMI Plone Admin can do various critical and important activities like managing catalog and indexes etc. which can be considered as job DBA (Database Administrator).
In ZMI one can register/add python script. And using python script it was possible to delete the objects. The script is now not able delete the objects because the implementation of enhanced security to maintain integrity of system. I completely agree about integrity and consistency of the system. I was making point in different context.
Anyway, I will find out the other way to meet the requirement. Sorry, for embarrassing. you and thanks a lot for showing the roadmap of senaite lims.
sixlibrary for Python 2/3 compatibility during the migration. First steps towards Python3 will start next week, but we'll do little by little. The idea is to start with the easiest Archetype content types first - e.g. Method, AnalysisCategory, SampleType - and continue gradually with those that have more complexity. This will allow us to face the challenges we may encounter little by little until the whole dance is done. We also plan to setup a migration utility that we will keep updating at the same pace we are porting things to Py3
senaite.jsonapi, which was initially planned as successor for the internal JSON API that ships currently with
senaite.core. The Sample creation does currently not work with the internal JSON API only, but should work with