Eins,
Your approach is a little odd, but nothing wrong with it, I suppose.
Typically, Events are the original bucket you pour your content into – and projects are sub-buckets from that.
Seems that you’re doing this a bit backwards, but there’s probably not a huge penalty in doing so because you can link multiple events to a project without penalty.
But arranging things this way DOES provide a bit of a challenge, IMO.
Metadata (including keywords, editing decisions and corrections) flow FROM import INTO events then INTO projects. There simply isn’t a very robust flow the other way. So while there’s no functional reason NOT to create multple events and link them to a single project – I’m not sure you’re gaining anything by creating mutliple events that you can’t do by creating ONE event and using multiple keywords and keyword collections to do any sorting or separating you need.
The big change in X compared to all other editors is how it uses the database and keywords rather than the finder and folders as the central organizing principle of the software.
I’d recommend you explore that. As you learn it better, think about how you might do what you want to do using keywords, rather than thinking of the Event browser as a construction of storages spaces or folders. That view might be too limiting in the long run.
Good luck.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor