In the MVP of federated properties, only remote properties can be used when federation is enabled. Local properties are not supported and will cause issues [See T255404]. Changes to the aliases, description, and/or label of a federated property should therefore only be possible on the source Wiki.
There are four special pages that interact with both items and properties in Wikibase, all of which have misleading names when federation is enabled:
* Special:SetAliases ("Set Item/Property aliases")
* Special:SetDescription ("Set Item/Property description")
* Special:SetLabel ("Set Item/Property label")
* Special:SetLabelDescriptionAliases ("Set Item/Property label, description and aliases")
See also T253863 for the Commons version of this issue wherein the page names mention too few entity types rather than too many.
**OptionsWe decided to go for a more temporary solution, which is to only change these page titles when federated properties are enabled (replacing Item/Property with Item). We will address this issue again in the next phase of federation in which local properties are possible, at which point we can explore something closer to option 3 below.
**BDD**
`Given` My Wikibase has federated properties enabled
`When` TBD
`Then` TBD
**Options We Considered**
# **Rename the pages to "Set Item [description, label, aliases]" -- for federated properties only, not across all Wikibase **
# Rename the pages to "Set Eplace item/property with entity [description, labelin the page title, aliases]" -- this would be in line with Wikidata special pages like EntitiesWithoutDescriptionthen list the available entity types somewhere else within the page
# Make pages more flexible and display the names of enabled entity types that have fingerprints and can be used with the page
**Initial Estimation**: 8 SPs