Revision Historyfor Stephen Baxter
for Stephen Baxter
| Revision ID | User | Note | Date |
|---|---|---|---|
| #211420 | indy133 | 2024-12-08 13:10:30 | |
| #211418 | indy133 | 2024-12-08 13:08:25 | |
| #188084 | indy133 | 2024-06-16 05:24:25 | |
| #188083 | indy133 | 2024-06-16 05:22:02 | |
| #187771 | indy133 | 2024-06-12 11:43:49 | |
| #187769 | indy133 | 2024-06-12 11:41:29 | |
| #187766 | indy133 | 2024-06-12 11:38:09 | |
| #164006 | indy133 | 2023-12-14 16:10:52 | |
| #77497 | Monkey | Book in hand—Monkey | 2021-12-02 12:44:23 |
| #77494 | Monkey | 2021-12-02 12:40:55 | |
| #55786 | indy133 | rel—indy133 Hi indy, I know you won't get a notification to read this yet but (soon) we will have revision-note notifications onsite!
afaik,this relationship (which is badly worded I agree) was intended, to be of the way "Author A collaborated on Joint Author-Group C" and "Artist B collaborated on Joint Author-Group C"
we will eventually have "artist credits" which I believe will solve this issue - there should be no real reason to create a third author with type group and linked as such, however author groups can and should still have members, think of it like members of a band.
infact it's from musical database this logic and rel comes from. I'd like your feedback and thoughts on this.—ApeKattQuest, MonkeyPython | 2021-03-08 19:34:04 |
| #53892 | Monkey | Corrections —Monkey | 2021-02-24 14:15:54 |
| #45836 | indy133 | 2020-12-02 17:23:10 | |
| #45835 | indy133 | 2020-12-02 17:22:01 | |
| #44246 | indy133 | 2020-11-21 08:13:12 | |
| #44244 | indy133 | 2020-11-21 08:01:34 | |
| #44243 | indy133 | place, rel—indy133 | 2020-11-21 08:00:22 |
| #39781 | indy133 | 2020-11-04 09:15:19 | |
| #39779 | indy133 | 2020-11-04 09:13:18 | |
| #32686 | Monkey | 2020-10-12 13:01:37 |