I am currently working on extending DSpace and need guidance on *creating a new table* while following DSpace’s best practices. Specifically, I am looking for the correct approach to:
1. *Defining a new model* that represents the new database table. 2. *Creating a corresponding DAO* that follows DSpace’s repository pattern. 3. *Integrating the new DAO with a service layer* for data management. 4. *Ensuring that the new table is correctly created in the database*, following the standard migration approach. I would appreciate it if you could provide insights on: - The preferred method for defining and registering a new *DAO and model* within the DSpace framework. - How to properly configure the *Spring-based repository layer* to interact with the database. - The correct way to *update the database schema*, ensuring that the new table is recognized during the migration process. If there are any existing examples, documentation references, or best practices for this process, I would be grateful if you could share them. Thank you in advance for your time and support. -- All messages to this mailing list should adhere to the Code of Conduct: https://www.lyrasis.org/about/Pages/Code-of-Conduct.aspx --- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to dspace-tech+unsubscr...@googlegroups.com. To view this discussion visit https://groups.google.com/d/msgid/dspace-tech/657a5848-a728-4a5a-9252-41578bc163b5n%40googlegroups.com.
