# Background Recently several departments for the university of Ljubljana, who each had their own membership, merged together as the University of Ljubljana. # Observed behavior Using Biotechnical Faculty as an example, if you search for "Biotechnical Faculty" here https://www.crossref.org/members/prep/, it tells you "No matching member name found. Please try again." If you search using the member ID in the URL: https://www.crossref.org/members/prep/5802, you'll get results, with numbers populated, but no name. (See attached screenshot.) This is what is happening for each of the moved prefixes. # Expected behavior [comment]: # (What did you expect to happen before you observed the anomalous behavior?) # How urgent [comment]: # (There are myriad factors that go into prioritizing and scheduling development work, but any information you can provide to help us understand severity, urgency, relative priority, or deadlines, is much appreciated.) [comment]: # (No need to update the Definition of ready when filing issues, but feel free to have a go if you're familiar with the territory.) # Definition of ready - [X] Product owner: @bvickery1 - [ ] Tech lead: - [X] Service:: label applied - [ ] Definition of done updated - [ ] Acceptance testing plan: - [ ] Weight applied [comment]: # (Feel free to leave this as is, or suggest changes. We'll update these during Backlog Refinement, prior to bringing this into a sprint.) # Definition of done - [ ] Unit tests identified, implemented, and passing - [ ] Code reviewed - [ ] Available for acceptance testing via a staging URL, or otherwise - [ ] Consider any impacts to current or future architecture/infrastructure, and update specifications and documentation as needed - [ ] Knowledge base reviewed and updated - [ ] Public documentation reviewed and updated - [ ] Acceptance criteria met - [ ] AC 1 - [ ] AC 2 - [ ] Acceptance testing passed # Notes [comment]: # (By default all issues need to be labeled Planning::New, only remove if you know what you're doing)