Many thanks Tim — this is just what I needed to know. Out of curiosity, if we were to turn on entities but not provide values in dspace.entity.type for existing records, would they automatically become publications, or would we still have to add the "Publication" value?
Best, Helen ________________________________ From: DSpace Community Sent: Friday, April 11, 2025 1:28 PM To: DSpace Community Subject: [dspace-community] Re: Question about entities & migration to 8 ** Caution: EXTERNAL Sender ** Hi Helen, At this time, Entities are still optional in all DSpace releases. They may eventually become required, but they are not required in version 8 or (the upcoming) version 9. If or when they do become required, we'd list that change in the Release Notes (in the "Breaking Changes" section). See the Release Notes for DSpace 8 for example: https://wiki.lyrasis.org/display/DSDOC8x/Release+Notes All that said, you are still welcome to try out Entities if you wish. Entities can be used *alongside* generic Items (there is no requirement to migrate everything to entities if you turn them on). It's also worth noting that generic Items are equivalent to "Publication" entities. But, when you turn on Entities, it provides you with new types of Items which can represent Person, Project, OrgUnit and the Journal hierarchy (Journal, Volume, Issue). I hope that clarifies things. If anything about this were to change in the future, we'd publish it in the Release Notes of that release. But, as I said, there are no changes to Entities in DSpace 8 or 9. Tim On Friday, April 11, 2025 at 1:39:28 PM UTC-5 Helen Baer wrote: Hello DSpace friends, We are on DSpace 7.6.2, and we're not using entities. I seem to recall hearing that entities would be required at some point, perhaps for 9. Is this true? I have read the documentation about entities<https://wiki.lyrasis.org/display/DSDOC8x/Configurable+Entities> <https://wiki.lyrasis.org/display/DSDOC8x/Configurable+Entities> for 8, and I have a basic understanding of how to implement entities using the dspace.entity.type metadata field, which we could use with one of the two default entity models, or configure locally (I suspect the former). We're trying to get a grip on how much work this would be if entities are required in the future. Best, Helen Helen Baer Digital Projects Librarian and Associate Professor Morgan Library Colorado State University Fort Collins, CO 80523-1019 Phone: 970-491-5934<tel:(970)%20491-5934> -- 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]<mailto:[email protected]>. To view this discussion visit https://groups.google.com/d/msgid/dspace-community/538a2fd0-b026-40aa-a10c-a9b2018f6b40n%40googlegroups.com<https://groups.google.com/d/msgid/dspace-community/538a2fd0-b026-40aa-a10c-a9b2018f6b40n%40googlegroups.com?utm_medium=email&utm_source=footer>. -- 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 Community" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/dspace-community/BY5PR07MB72650660C8439611D9EB50DE88B32%40BY5PR07MB7265.namprd07.prod.outlook.com.
