CiviCRM Community Forums (archive)

#1 Delete:
CiviMember >> Find Member >> check to ones you want to delete >> select delete members from the more actions drop down.
When  importing memberships, makes sure to use the source field so that you can easily search for imported memberships for cases just such as this.

#2:
Have you filled an enhancement request outlining how you think the membership import should be improved?
http://wiki.civicrm.org/confluence/display/CRMDOC/File+Issue

Thanks for the responses guys. I've been away on hols, so sorry for not getting back sooner.

geilhufe, regarding your comments,

#1 Delete:
CiviMember >> Find Member >> check to ones you want to delete >> select delete members from the more actions drop down.
When  importing memberships, makes sure to use the source field so that you can easily search for imported memberships for cases just such as this.

I think the issue I've got with the CiviMember module is that the search function is restricted to fields contained within the CiviMember module. So if I've got 200 memberships to delete, I'll have to do each one by hand, rather than searching by tags or groups for example. I understand the logic behind restricting the search for members criteria to fields contained within the membership module, but I'm a little restricted as to what I can do otherwise.

The double memberships aren't an issue really as they have the same start and end dates so will exipre and function normally under the current system we are using.

James.

Geilhufe - I've just spent a week or so working on some data. I'm working at an educational institute that produces a magazine, and unfortunately the two systems are kept separately. Each student is entitled to membership, and this status will change depending on which year they're in, whether they graduate/defer/drop out, when they enrolled and so on.
The job of updating the memberships at the beginning of the academic year has been a logistical nightmare, and would have been even if I was using either of the previous CRMs that I'd worked with.
A couple of things that would have helped me on my way:

1. "It would be cool if you could use "batch update via profile" to update the source ID, but you can't". Batch updating all membership fields via profile in the contact search - or improving the search functions in the membership module and allowing batch updating there.

2. "It would be cool if you could use "update" functionality on the member import like on the contact import, but you can't". Unfortunately I had to export a list of students in the contact section, do a search for a specific expiry date (which they all fortunately had), delete the individual memberships I needed to update and import the updated memberships. Being able to update on member import would have saved me all this work.

The member and contribution modules are extremely useful and in time will be improved I'm sure. An easy way to make us database administrators happy would be to make them on a par with contacts in terms of search, batch update, export from and import to regarding their functionality.

Always aware of posting on these forums that CiviCRM is free, so please, if any of the developers reads this, don't take the above as harsh criticism, but suggestions of functionality. Thanks for the product.

James.