35:
198:(even if the direct link no longer works at least it informs the right provider). I don't want to be in a position where links are deleted and someone complains and we have an argument and I have to restore etc.. it should be discussed first. Since they currently exist in the system and are dead I will go ahead and save them with archive URLs. But to
222:
OK, thanks for adding the archive URLs. I agree that the archive URLs do somewhat usefully indicate that the source is (or, perhaps in some cases, was) available in an EBSCOhost database, but it also seems a little silly to archive an URL that is not the cited source but just another citation of the
197:
all of these links that is beyond the bot's approval. There is an argument for keeping the links, they contain metadata that may not be in the citation itself allowing for easier verification of the source, they also indicate the source is available in the EBSCOhost database which is useful to know
174:
to a citation in an article. The citation was fine without the JSTOR number; the addition of the JSTOR number just gives another way to access the source. The EBSCOhost
Connection URLs are analogous to the JSTOR number, except that now EBSCOhost Connection does
110:
says that EBSCOhost
Connection is deprecated and there is no way to remap the broken links to new URLs. Would someone be willing to write and run a bot to remove the broken links to EBSCOhost Connection (URLs beginning with
83:
202:
them from
Knowledge (XXG) is a separate idea, if there is consensus let me know I will go back and unwind the archives, except for the bare and square links. --
135:
21:
134:. I'd like to do more research and verify there is another way to save them. Worst case are archive URLs so they wouldn't need to be removed.
73:
292:
232:
217:
188:
153:
124:
162:
without any of the other information required to locate the source. EBSCOhost is just a provider of article databases, like
170:. It's one of various ways to access the cited source; it's not the cited source itself. Another example would be how I
179:
give another way to access the source, so the EBSCOhost
Connection URLs should be removed unless they are bare URLs.
42:
223:
cited source (so it's a citation of an archive of a citation). But it's the easiest way to handle the situation.
228:
184:
120:
265:, for discovering this. Whenever or if, the bot can delete the URLs and remove "EBSCOhost" from fields like
171:
103:
159:
99:
51:
17:
262:
224:
180:
116:
131:
285:
210:
146:
95:
84:
Knowledge (XXG):Help desk/Archives/2020 November 8 § Broken EBSCOhost
Connection links
278:
203:
158:
Thanks. In my opinion, it would only be necessary to save the URLs if they were
139:
50:
If you wish to start a new discussion or revive an old one, please do so on the
91:
167:
163:
112:
107:
29:
115:) from cited sources in Knowledge (XXG) articles? Thanks,
87:
193:I can save links with archive URLs, but as for
8:
274:
270:
266:
48:Do not edit the contents of this page.
7:
28:
33:
113:http://connection.ebscohost.com
1:
293:03:04, 20 November 2020 (UTC)
233:18:50, 19 November 2020 (UTC)
218:18:28, 19 November 2020 (UTC)
189:17:31, 19 November 2020 (UTC)
172:recently added a JSTOR number
154:17:13, 19 November 2020 (UTC)
125:16:48, 19 November 2020 (UTC)
98:in Knowledge (XXG) articles.
248:Added 1,069 new archive URLs
308:
86:, I noted that there are
18:Knowledge (XXG):Link rot
102:did some research and
74:Village Pump Technical
72:Post copied here from
46:of past discussions.
64:EBSCOhost Connection
130:This something for
22:URL change requests
257:(list on request)
88:many broken links
78:
58:
57:
52:current main page
299:
290:
283:
276:
272:
268:
256:
255:
215:
208:
151:
144:
100:Samwalton9 (WMF)
76:
69:
37:
36:
30:
307:
306:
302:
301:
300:
298:
297:
296:
286:
279:
253:
252:
211:
204:
147:
140:
71:
66:
34:
26:
25:
24:
12:
11:
5:
305:
303:
263:Biogeographist
259:
258:
249:
242:
241:
240:
239:
238:
237:
236:
235:
225:Biogeographist
181:Biogeographist
117:Biogeographist
94:Connection in
80:
79:
65:
62:
60:
56:
55:
38:
27:
15:
14:
13:
10:
9:
6:
4:
3:
2:
304:
295:
294:
291:
289:
284:
282:
264:
254:{{dead link}}
250:
247:
246:
245:
244:Bot results:
234:
230:
226:
221:
220:
219:
216:
214:
209:
207:
201:
196:
192:
191:
190:
186:
182:
178:
173:
169:
165:
161:
157:
156:
155:
152:
150:
145:
143:
137:
133:
129:
128:
127:
126:
122:
118:
114:
109:
105:
101:
97:
96:cited sources
93:
89:
85:
77:
75:
68:
67:
63:
61:
53:
49:
45:
44:
39:
32:
31:
23:
19:
287:
280:
260:
243:
212:
205:
199:
194:
176:
148:
141:
81:
70:
59:
47:
41:
267:|publisher=
261:Thank you,
40:This is an
251:Added 371
160:bare URLs
132:WP:URLREQ
92:EBSCOhost
195:deleting
168:ProQuest
104:reported
20: |
136:Example
43:archive
275:|work=
200:delete
281:Green
277:. --
271:|via=
206:Green
164:JSTOR
142:Green
138:. --
108:EBSCO
106:that
16:<
273:and
229:talk
185:talk
121:talk
177:not
166:or
90:to
82:At
269:,
231:)
187:)
123:)
288:C
227:(
213:C
183:(
149:C
119:(
54:.
Text is available under the Creative Commons Attribution-ShareAlike License. Additional terms may apply.