In our instance of 5.1, resource IDs are being reused when new groups are created. We've created new groups that have reused the ID numbers of already existing communities. The newly created groups do not appear in the list of all groups.
The problem is that an ID for a group is guaranteed unique for the epersongroup table and a community ID is guaranteed unique for the community table, but there is nothing to keep both from appearing in the metadatavalue table as resource IDs. We've got items groups collections and communities all with the same resource_id in the metadatavalue table. Chris Gray Systems Analyst 519-888-4567, ext. 35764 cpg...@uwaterloo.ca University of Waterloo ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
