Domain Access Taxonomy vs. Domain Taxonomy

I would recommend that the maintainer of this module consider either offering to co-maintain Domain Taxonomy and work on making that project better instead, or deprecate the 7.x branch of that module in favor of this one.

(Edited my post because, after browsing both repositories, this module looks better architected in D7.)

[Unrelated old man grumble] I wonder if we need a sign-off process for promoting projects to start reducing from duplicates, this seems to be happening a lot recently, especially in the last few months (this makes 3 that have come to my attention in the last week alone). With 8,000 full and about the same # sandboxes this is getting hard to track...

@skizzo I saw in the queues that you were needing to restrict access per domain, which from reading the code & project description, this one will not help much. It targets the core taxonomy term widget on the node form to reduce options, but that appears to be it. It is a filter only afaick. Free tagging would completely bypass this as in the other module (although there is a patch for that there)

So if you use Entity Reference, then this will not restrict that widget. Same for tag clouds or any other related taxonomy functions.

And in relation to "is minimally maintained", so this one is better?!

@xjm The main project is a mess, but it offers a lot more (somewhat broken) functionality. This one is cleaner as it doesn't do much.

In relation to access control, Domain Taxonomy handles this with a query access alter which is perfect, but (from reading Entity Reference code), core does not add any access tags on the field widgets.

Personally I would want to write them both off and start afresh with an entity based access model (aka one base modal for everything - including DA core itself), but that would take a solid weeks work just to do the base groundwork. I know because I rewrote Domain Source to do this about two weeks back to get a domain ownership flag set on all entities on the system :)

all I can say is to be really nice to Nick and see if he can push out a few bug fixes.

I've update the project status ... not in a positive way ;)