> Rather than jumping directly to development proposals with > specific > companies or individuals, I would suggest opening a bug at > http://bugs.launchpad.net/evergreen with the details so that all > Evergreen developers can discuss the best way forward for ensuring > that > we handle this in the Evergreen 2.4 release. There are a number of > potential ways of handling both the indexing and display side of > things.
+1 also. I was searching earlier this week to see if there were any RDA related bugs open yet, but I haven't made time to create any myself. > >> Sorry if this email sounds frantic- I am not a cataloger- I kept >> hearing that RDA was coming- and I sort of hid my head in the >> sand.... >> I guess I will always be a reference librarian at heart. >> #catalogerswereright As gratifying as it is to see that hashtag, plenty of us are hiding our heads in the sand as well! > > There are a number of other RDA changes to address as well. Having > one > or more bugs with clear directions on what the community wants > will help > all of us! Since there are several things that need development, some of which are probably only related in that they are required by RDA, multiple tickets probably make the most sense. I'd suggest tagging them rda so that they're easy to find. Sarah Childs Senior Cataloger Hussey-Mayfield Memorial Public Library 250 North Fifth Street Zionsville, IN 46077 317-873-3149 x13330 [email protected]
