Description
Arrange supplied community and authority credits in the requested order.
Community-supplied names, credits, permissions and source versions carry their own authority and context. A recorded access or precision label does not itself grant permission or hide a location. Preserving requested wording and attribution order is distinct from authenticating rights, community approval or adequate protection.
Arrange supplied community and authority credits in the requested order.
When to use this tool
Use Community Attribution Authority Order when you already have communityCredit, suppliedAuthorityCredit, communityFirst and need to arrange supplied community and authority credits in the requested order.
How to use the tool and how it works
- Enter communityCredit, suppliedAuthorityCredit, communityFirst. Use the units and conventions below.
- Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
- Read creditLine. Use the output convention below.
Require both credit texts nonempty; join them with semicolon-space, putting community first only when communityFirst=true.1
| Input field | Meaning and units | Accepted input |
|---|---|---|
| communityCredit | Community Credit | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| suppliedAuthorityCredit | Supplied Authority Credit | Required. Text; minimum UTF-16 length 1; maximum UTF-16 length 8192. |
| communityFirst | Display order of supplied credit strings; does not establish attribution authority. | Required. Boolean. |
| Output field | Interpretation | Returned shape |
|---|---|---|
| creditLine | Credit Line | Required. Text; maximum UTF-16 length 8192. |
{
"input": {
"communityCredit": "Community A",
"suppliedAuthorityCredit": "Authority record B",
"communityFirst": true
},
"output": {
"creditLine": "Community A; Authority record B"
}
}Limitations and assumptions
- Credits are supplied rather than assigned or verified; ordering does not establish attribution authority, consent or publication rights.
- Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
Alternative or Complementary methods
Consult the original community-provided permissions, attribution instructions and controlled records for actual use. Apply access and location protection to the underlying material, rather than treating a display mask or status label as the complete safeguard.
References
Similar or alternative tools
- Community Preferred Name Period Label
Preserve an explicitly supplied community preferred-name and period label.
- Community Approval Version Date Pair
Preserve an explicit community-approval version-date record.