JS
Joe Slag
Wed, Sep 14, 2011 3:10 PM
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
HH
Heather Hart
Wed, Sep 14, 2011 4:55 PM
Thanks Joe, I am going to fix this, I think it's just a linking problem.
-----Original Message-----
From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Joe Slag
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure step checklist", are links to pages that have been moved or deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows confluence to make a good guess about their location, but still presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that important, but I thought I'd mention it given 1.8's positioning as a thoroughly-QA'd release. Also it might be nice to identify whatever process problems led to this problem so that it can be avoided for future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thanks Joe, I am going to fix this, I think it's just a linking problem.
-----Original Message-----
From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Joe Slag
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure step checklist", are links to pages that have been moved or deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows confluence to make a good guess about their location, but still presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that important, but I thought I'd mention it given 1.8's positioning as a thoroughly-QA'd release. Also it might be nice to identify whatever process problems led to this problem so that it can be avoided for future releases.
cheers,
Joe
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
HH
Heather Hart
Thu, Sep 15, 2011 7:26 PM
Hi Joe,
One documentation issue always leads to several dozen more. This is really two separate problems.
First of all, these pages were not copied over because at the time the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued these pages from the main wiki where they were buried. If you look at the 1.9 wiki space, these pages have been moved over and appear in the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki, the links are still broken. The links did not travel well because they are hard-linked (it is linked as a standard hyperlink: http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration) so when we "rescued" these pages, it also broke these links. Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links. This is a great reminder to everyone to use the fluid tools when editing the wiki pages. In this particular case, there is a child pages macro that would work perfectly. Under normal circumstances it is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages. The 1.9 wiki will include the "rescued" pages, but would not include the fruits of our most recent documentation push (much of which may apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and then use the child macro instead of the hard-coded list so Joe can continue his work. I am having a bit of a time with this, since I keep getting connection errors and "error retrieving breadcrumbs" problems. Is anyone else having trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Joe,
One documentation issue always leads to several dozen more. This is really two separate problems.
First of all, these pages were not copied over because at the time the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued these pages from the main wiki where they were buried. If you look at the 1.9 wiki space, these pages have been moved over and appear in the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki, the links are still broken. The links did not travel well because they are hard-linked (it is linked as a standard hyperlink: http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration) so when we "rescued" these pages, it also broke these links. Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links. This is a great reminder to everyone to use the fluid tools when editing the wiki pages. In this particular case, there is a child pages macro that would work perfectly. Under normal circumstances it is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages. The 1.9 wiki will include the "rescued" pages, but would not include the fruits of our most recent documentation push (much of which may apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and then use the child macro instead of the hard-coded list so Joe can continue his work. I am having a bit of a time with this, since I keep getting connection errors and "error retrieving breadcrumbs" problems. Is anyone else having trouble with the wiki?
Heather
________________________________________
From: talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
JM
Jesse Martinez
Thu, Sep 15, 2011 10:08 PM
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be
aware of any recent changes to 1.9. Although, I make the assumption that
some changes may have occurred on both 1.8 as well as 1.9 so in that case
it's moot. The trouble with links is a big one and if we can straighten it
with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
We just need to make the concerted effort to follow every lin on every page
to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was this
recently? Did you also see issues with jira or any of our other services?
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart hhart@bpoc.org wrote:
Hi Joe,
One documentation issue always leads to several dozen more. This is really
two separate problems.
First of all, these pages were not copied over because at the time the 1.8
wiki was mirrored from UNRELEASED, we had not yet rescued these pages from
the main wiki where they were buried. If you look at the 1.9 wiki space,
these pages have been moved over and appear in the heirarchy (left sidebar)
under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki,
the links are still broken. The links did not travel well because they are
hard-linked (it is linked as a standard hyperlink:
http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration)
so when we "rescued" these pages, it also broke these links. Unfortunately,
the fluid tools can't tell us (as far as I know) when we break hard links.
This is a great reminder to everyone to use the fluid tools when editing the
wiki pages. In this particular case, there is a child pages macro that would
work perfectly. Under normal circumstances it is best to link to another
cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad
shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki
into 1.8? This is risky if people have been making changes to the 1.8 pages.
The 1.9 wiki will include the "rescued" pages, but would not include the
fruits of our most recent documentation push (much of which may apply to
1.8?).
For now I am going to manually move these pages back into 1.8 and then use
the child macro instead of the hard-coded list so Joe can continue his work.
I am having a bit of a time with this, since I keep getting connection
errors and "error retrieving breadcrumbs" problems. Is anyone else having
trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org [
talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [
joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example,
http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be
aware of any recent changes to 1.9. Although, I make the assumption that
some changes may have occurred on both 1.8 as well as 1.9 so in that case
it's moot. The trouble with links is a big one and if we can straighten it
with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
We just need to make the concerted effort to follow every lin on every page
to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was this
recently? Did you also see issues with jira or any of our other services?
- Jesse
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart <hhart@bpoc.org> wrote:
> Hi Joe,
>
> One documentation issue always leads to several dozen more. This is really
> two separate problems.
>
> First of all, these pages were not copied over because at the time the 1.8
> wiki was mirrored from UNRELEASED, we had not yet rescued these pages from
> the main wiki where they were buried. If you look at the 1.9 wiki space,
> these pages have been moved over and appear in the heirarchy (left sidebar)
> under the appropriate page.
>
> Secondly, even though the pages exist where they should in the 1.9 wiki,
> the links are still broken. The links did not travel well because they are
> hard-linked (it is linked as a standard hyperlink:
> http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration)
> so when we "rescued" these pages, it also broke these links. Unfortunately,
> the fluid tools can't tell us (as far as I know) when we break hard links.
> This is a great reminder to everyone to use the fluid tools when editing the
> wiki pages. In this particular case, there is a child pages macro that would
> work perfectly. Under normal circumstances it is best to link to another
> cspace wiki page by using the search function on the edit link screen.
>
> So, in terms of what we can and should do, the 1.8 wiki is in pretty bad
> shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki
> into 1.8? This is risky if people have been making changes to the 1.8 pages.
> The 1.9 wiki will include the "rescued" pages, but would not include the
> fruits of our most recent documentation push (much of which may apply to
> 1.8?).
>
> For now I am going to manually move these pages back into 1.8 and then use
> the child macro instead of the hard-coded list so Joe can continue his work.
> I am having a bit of a time with this, since I keep getting connection
> errors and "error retrieving breadcrumbs" problems. Is anyone else having
> trouble with the wiki?
>
> Heather
> ________________________________________
> From: talk-bounces@lists.collectionspace.org [
> talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [
> joe@slagwerks.com]
> Sent: Wednesday, September 14, 2011 8:10 AM
> To: CollectionSpace Talk List
> Subject: [Talk] changed / deprecated links in 1.8 docs
>
> I was just referring to
>
> http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
> and noticed that many of the details, under the heading "Procedure
> step checklist", are links to pages that have been moved or
> deprectated.
>
> For example,
> http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
> is linked to in step 2b. The top of that page says in red:
>
> REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
> THE UI SCHEMA FILE)
>
> Many of the other pages seem to have been moved in a way that allows
> confluence to make a good guess about their location, but still
> presents an intermediate 'page moved' page.
>
> If this was just any old release I don't think it would be that
> important, but I thought I'd mention it given 1.8's positioning as a
> thoroughly-QA'd release. Also it might be nice to identify whatever
> process problems led to this problem so that it can be avoided for
> future releases.
>
> cheers,
> Joe
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
>
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
AR
Aron Roberts
Thu, Sep 15, 2011 10:51 PM
PLEASE READ before 'mirroring' any docs
Many of the key v1.8 docs are very different than their v1.9 counterparts:
-
Some of the Installing CollectionSpace docs for v1.8 are (at least)
slightly different than their 1.9 counterparts.
-
At least one or two of the core Configuring CollectionSpace docs
differ substantially from their 1.9 counterparts, to reflect that the
app layer configuration changed to a new overlay structure in v1.9.
Before doing any wholesale 'mirroring', it might be good to check a
chronological list of recently updated documents, and/or review which
documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be
aware of any recent changes to 1.9. Although, I make the assumption that
some changes may have occurred on both 1.8 as well as 1.9 so in that case
it's moot. The trouble with links is a big one and if we can straighten it
with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
We just need to make the concerted effort to follow every lin on every page
to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was this
recently? Did you also see issues with jira or any of our other services?
- Jesse
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart hhart@bpoc.org wrote:
Hi Joe,
One documentation issue always leads to several dozen more. This is really
two separate problems.
First of all, these pages were not copied over because at the time the 1.8
wiki was mirrored from UNRELEASED, we had not yet rescued these pages from
the main wiki where they were buried. If you look at the 1.9 wiki space,
these pages have been moved over and appear in the heirarchy (left sidebar)
under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki,
the links are still broken. The links did not travel well because they are
hard-linked (it is linked as a standard hyperlink:
http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration)
so when we "rescued" these pages, it also broke these links. Unfortunately,
the fluid tools can't tell us (as far as I know) when we break hard links.
This is a great reminder to everyone to use the fluid tools when editing the
wiki pages. In this particular case, there is a child pages macro that would
work perfectly. Under normal circumstances it is best to link to another
cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad
shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki
into 1.8? This is risky if people have been making changes to the 1.8 pages.
The 1.9 wiki will include the "rescued" pages, but would not include the
fruits of our most recent documentation push (much of which may apply to
1.8?).
For now I am going to manually move these pages back into 1.8 and then use
the child macro instead of the hard-coded list so Joe can continue his work.
I am having a bit of a time with this, since I keep getting connection
errors and "error retrieving breadcrumbs" problems. Is anyone else having
trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org
[talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
[joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example,
http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
*******PLEASE READ before 'mirroring' any docs*******
Many of the key v1.8 docs are very different than their v1.9 counterparts:
* Some of the Installing CollectionSpace docs for v1.8 are (at least)
slightly different than their 1.9 counterparts.
* At least one or two of the core Configuring CollectionSpace docs
differ substantially from their 1.9 counterparts, to reflect that the
app layer configuration changed to a new overlay structure in v1.9.
Before doing any wholesale 'mirroring', it might be good to check a
chronological list of recently updated documents, and/or review which
documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez
<jmartinez@movingimage.us> wrote:
> Heather,
> I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be
> aware of any recent changes to 1.9. Although, I make the assumption that
> some changes may have occurred on both 1.8 as well as 1.9 so in that case
> it's moot. The trouble with links is a big one and if we can straighten it
> with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
> We just need to make the concerted effort to follow every lin on every page
> to make sure it's pointing in the right location.
> I'm not aware of any time out issues for me/us on the east coast. Was this
> recently? Did you also see issues with jira or any of our other services?
> - Jesse
>
> On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart <hhart@bpoc.org> wrote:
>>
>> Hi Joe,
>>
>> One documentation issue always leads to several dozen more. This is really
>> two separate problems.
>>
>> First of all, these pages were not copied over because at the time the 1.8
>> wiki was mirrored from UNRELEASED, we had not yet rescued these pages from
>> the main wiki where they were buried. If you look at the 1.9 wiki space,
>> these pages have been moved over and appear in the heirarchy (left sidebar)
>> under the appropriate page.
>>
>> Secondly, even though the pages exist where they should in the 1.9 wiki,
>> the links are still broken. The links did not travel well because they are
>> hard-linked (it is linked as a standard hyperlink:
>> http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration)
>> so when we "rescued" these pages, it also broke these links. Unfortunately,
>> the fluid tools can't tell us (as far as I know) when we break hard links.
>> This is a great reminder to everyone to use the fluid tools when editing the
>> wiki pages. In this particular case, there is a child pages macro that would
>> work perfectly. Under normal circumstances it is best to link to another
>> cspace wiki page by using the search function on the edit link screen.
>>
>> So, in terms of what we can and should do, the 1.8 wiki is in pretty bad
>> shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki
>> into 1.8? This is risky if people have been making changes to the 1.8 pages.
>> The 1.9 wiki will include the "rescued" pages, but would not include the
>> fruits of our most recent documentation push (much of which may apply to
>> 1.8?).
>>
>> For now I am going to manually move these pages back into 1.8 and then use
>> the child macro instead of the hard-coded list so Joe can continue his work.
>> I am having a bit of a time with this, since I keep getting connection
>> errors and "error retrieving breadcrumbs" problems. Is anyone else having
>> trouble with the wiki?
>>
>> Heather
>> ________________________________________
>> From: talk-bounces@lists.collectionspace.org
>> [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
>> [joe@slagwerks.com]
>> Sent: Wednesday, September 14, 2011 8:10 AM
>> To: CollectionSpace Talk List
>> Subject: [Talk] changed / deprecated links in 1.8 docs
>>
>> I was just referring to
>>
>> http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
>> and noticed that many of the details, under the heading "Procedure
>> step checklist", are links to pages that have been moved or
>> deprectated.
>>
>> For example,
>> http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
>> is linked to in step 2b. The top of that page says in red:
>>
>> REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
>> THE UI SCHEMA FILE)
>>
>> Many of the other pages seem to have been moved in a way that allows
>> confluence to make a good guess about their location, but still
>> presents an intermediate 'page moved' page.
>>
>> If this was just any old release I don't think it would be that
>> important, but I thought I'd mention it given 1.8's positioning as a
>> thoroughly-QA'd release. Also it might be nice to identify whatever
>> process problems led to this problem so that it can be avoided for
>> future releases.
>>
>> cheers,
>> Joe
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>>
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
>
HH
Heather Hart
Fri, Sep 16, 2011 2:54 PM
I have gotten all of these pages moved and re-linked.
Rick, you marked this page as outdated back in February: http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
This makes me concerned that the whole section is out of date or incorrect. Can you please review http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued for accuracy as of 1.8?
Joe, if/when you make changes to this section, could you give me a heads up? Thanks,
Heather
From: talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.org] on behalf of Heather Hart [hhart@bpoc.org]
Sent: Thursday, September 15, 2011 12:26 PM
To: Joe Slag; CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
Hi Joe,
One documentation issue always leads to several dozen more. This is really two separate problems.
First of all, these pages were not copied over because at the time the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued these pages from the main wiki where they were buried. If you look at the 1.9 wiki space, these pages have been moved over and appear in the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki, the links are still broken. The links did not travel well because they are hard-linked (it is linked as a standard hyperlink: http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration) so when we "rescued" these pages, it also broke these links. Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links. This is a great reminder to everyone to use the fluid tools when editing the wiki pages. In this particular case, there is a child pages macro that would work perfectly. Under normal circumstances it is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages. The 1.9 wiki will include the "rescued" pages, but would not include the fruits of our most recent documentation push (much of which may apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and then use the child macro instead of the hard-coded list so Joe can continue his work. I am having a bit of a time with this, since I keep getting connection errors and "error retrieving breadcrumbs" problems. Is anyone else having trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
I have gotten all of these pages moved and re-linked.
Rick, you marked this page as outdated back in February: http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
This makes me concerned that the whole section is out of date or incorrect. Can you please review http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued for accuracy as of 1.8?
Joe, if/when you make changes to this section, could you give me a heads up? Thanks,
Heather
________________________________________
From: talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.org] on behalf of Heather Hart [hhart@bpoc.org]
Sent: Thursday, September 15, 2011 12:26 PM
To: Joe Slag; CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
Hi Joe,
One documentation issue always leads to several dozen more. This is really two separate problems.
First of all, these pages were not copied over because at the time the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued these pages from the main wiki where they were buried. If you look at the 1.9 wiki space, these pages have been moved over and appear in the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki, the links are still broken. The links did not travel well because they are hard-linked (it is linked as a standard hyperlink: http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration) so when we "rescued" these pages, it also broke these links. Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links. This is a great reminder to everyone to use the fluid tools when editing the wiki pages. In this particular case, there is a child pages macro that would work perfectly. Under normal circumstances it is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages. The 1.9 wiki will include the "rescued" pages, but would not include the fruits of our most recent documentation push (much of which may apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and then use the child macro instead of the hard-coded list so Joe can continue his work. I am having a bit of a time with this, since I keep getting connection errors and "error retrieving breadcrumbs" problems. Is anyone else having trouble with the wiki?
Heather
________________________________________
From: talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
HH
Heather Hart
Fri, Sep 16, 2011 2:57 PM
Thanks for your input Jesse and Aron. We will have to talk about this more in some detail before we move on it. There are a lot of moving pieces.
Heather
From: Aron Roberts [aronroberts@gmail.com]
Sent: Thursday, September 15, 2011 3:51 PM
To: Jesse Martinez; Heather Hart
Cc: CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
PLEASE READ before 'mirroring' any docs
Many of the key v1.8 docs are very different than their v1.9 counterparts:
-
Some of the Installing CollectionSpace docs for v1.8 are (at least)
slightly different than their 1.9 counterparts.
-
At least one or two of the core Configuring CollectionSpace docs
differ substantially from their 1.9 counterparts, to reflect that the
app layer configuration changed to a new overlay structure in v1.9.
Before doing any wholesale 'mirroring', it might be good to check a
chronological list of recently updated documents, and/or review which
documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez
jmartinez@movingimage.us wrote:
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be
aware of any recent changes to 1.9. Although, I make the assumption that
some changes may have occurred on both 1.8 as well as 1.9 so in that case
it's moot. The trouble with links is a big one and if we can straighten it
with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
We just need to make the concerted effort to follow every lin on every page
to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was this
recently? Did you also see issues with jira or any of our other services?
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart hhart@bpoc.org wrote:
Hi Joe,
One documentation issue always leads to several dozen more. This is really
two separate problems.
First of all, these pages were not copied over because at the time the 1.8
wiki was mirrored from UNRELEASED, we had not yet rescued these pages from
the main wiki where they were buried. If you look at the 1.9 wiki space,
these pages have been moved over and appear in the heirarchy (left sidebar)
under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki,
the links are still broken. The links did not travel well because they are
hard-linked (it is linked as a standard hyperlink:
http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration)
so when we "rescued" these pages, it also broke these links. Unfortunately,
the fluid tools can't tell us (as far as I know) when we break hard links.
This is a great reminder to everyone to use the fluid tools when editing the
wiki pages. In this particular case, there is a child pages macro that would
work perfectly. Under normal circumstances it is best to link to another
cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad
shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki
into 1.8? This is risky if people have been making changes to the 1.8 pages.
The 1.9 wiki will include the "rescued" pages, but would not include the
fruits of our most recent documentation push (much of which may apply to
1.8?).
For now I am going to manually move these pages back into 1.8 and then use
the child macro instead of the hard-coded list so Joe can continue his work.
I am having a bit of a time with this, since I keep getting connection
errors and "error retrieving breadcrumbs" problems. Is anyone else having
trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org
[talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
[joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example,
http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Thanks for your input Jesse and Aron. We will have to talk about this more in some detail before we move on it. There are a lot of moving pieces.
Heather
________________________________________
From: Aron Roberts [aronroberts@gmail.com]
Sent: Thursday, September 15, 2011 3:51 PM
To: Jesse Martinez; Heather Hart
Cc: CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
*******PLEASE READ before 'mirroring' any docs*******
Many of the key v1.8 docs are very different than their v1.9 counterparts:
* Some of the Installing CollectionSpace docs for v1.8 are (at least)
slightly different than their 1.9 counterparts.
* At least one or two of the core Configuring CollectionSpace docs
differ substantially from their 1.9 counterparts, to reflect that the
app layer configuration changed to a new overlay structure in v1.9.
Before doing any wholesale 'mirroring', it might be good to check a
chronological list of recently updated documents, and/or review which
documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez
<jmartinez@movingimage.us> wrote:
> Heather,
> I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be
> aware of any recent changes to 1.9. Although, I make the assumption that
> some changes may have occurred on both 1.8 as well as 1.9 so in that case
> it's moot. The trouble with links is a big one and if we can straighten it
> with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
> We just need to make the concerted effort to follow every lin on every page
> to make sure it's pointing in the right location.
> I'm not aware of any time out issues for me/us on the east coast. Was this
> recently? Did you also see issues with jira or any of our other services?
> - Jesse
>
> On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart <hhart@bpoc.org> wrote:
>>
>> Hi Joe,
>>
>> One documentation issue always leads to several dozen more. This is really
>> two separate problems.
>>
>> First of all, these pages were not copied over because at the time the 1.8
>> wiki was mirrored from UNRELEASED, we had not yet rescued these pages from
>> the main wiki where they were buried. If you look at the 1.9 wiki space,
>> these pages have been moved over and appear in the heirarchy (left sidebar)
>> under the appropriate page.
>>
>> Secondly, even though the pages exist where they should in the 1.9 wiki,
>> the links are still broken. The links did not travel well because they are
>> hard-linked (it is linked as a standard hyperlink:
>> http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration)
>> so when we "rescued" these pages, it also broke these links. Unfortunately,
>> the fluid tools can't tell us (as far as I know) when we break hard links.
>> This is a great reminder to everyone to use the fluid tools when editing the
>> wiki pages. In this particular case, there is a child pages macro that would
>> work perfectly. Under normal circumstances it is best to link to another
>> cspace wiki page by using the search function on the edit link screen.
>>
>> So, in terms of what we can and should do, the 1.8 wiki is in pretty bad
>> shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki
>> into 1.8? This is risky if people have been making changes to the 1.8 pages.
>> The 1.9 wiki will include the "rescued" pages, but would not include the
>> fruits of our most recent documentation push (much of which may apply to
>> 1.8?).
>>
>> For now I am going to manually move these pages back into 1.8 and then use
>> the child macro instead of the hard-coded list so Joe can continue his work.
>> I am having a bit of a time with this, since I keep getting connection
>> errors and "error retrieving breadcrumbs" problems. Is anyone else having
>> trouble with the wiki?
>>
>> Heather
>> ________________________________________
>> From: talk-bounces@lists.collectionspace.org
>> [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
>> [joe@slagwerks.com]
>> Sent: Wednesday, September 14, 2011 8:10 AM
>> To: CollectionSpace Talk List
>> Subject: [Talk] changed / deprecated links in 1.8 docs
>>
>> I was just referring to
>>
>> http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
>> and noticed that many of the details, under the heading "Procedure
>> step checklist", are links to pages that have been moved or
>> deprectated.
>>
>> For example,
>> http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
>> is linked to in step 2b. The top of that page says in red:
>>
>> REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
>> THE UI SCHEMA FILE)
>>
>> Many of the other pages seem to have been moved in a way that allows
>> confluence to make a good guess about their location, but still
>> presents an intermediate 'page moved' page.
>>
>> If this was just any old release I don't think it would be that
>> important, but I thought I'd mention it given 1.8's positioning as a
>> thoroughly-QA'd release. Also it might be nice to identify whatever
>> process problems led to this problem so that it can be avoided for
>> future releases.
>>
>> cheers,
>> Joe
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>>
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
>
HH
Heather Hart
Tue, Sep 20, 2011 12:37 AM
Hi Jesse,
The wiki has been fine today. I will let you know if anything else crops up and am going to blame it on crappy free wifi for now.
Heather
From: Jesse Martinez [mailto:jmartinez@movingimage.us]
Sent: Thursday, September 15, 2011 3:09 PM
To: Heather Hart
Cc: Joe Slag; CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be aware of any recent changes to 1.9. Although, I make the assumption that some changes may have occurred on both 1.8 as well as 1.9 so in that case it's moot. The trouble with links is a big one and if we can straighten it with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on. We just need to make the concerted effort to follow every lin on every page to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was this recently? Did you also see issues with jira or any of our other services?
One documentation issue always leads to several dozen more. This is really two separate problems.
First of all, these pages were not copied over because at the time the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued these pages from the main wiki where they were buried. If you look at the 1.9 wiki space, these pages have been moved over and appear in the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki, the links are still broken. The links did not travel well because they are hard-linked (it is linked as a standard hyperlink: http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration) so when we "rescued" these pages, it also broke these links. Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links. This is a great reminder to everyone to use the fluid tools when editing the wiki pages. In this particular case, there is a child pages macro that would work perfectly. Under normal circumstances it is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages. The 1.9 wiki will include the "rescued" pages, but would not include the fruits of our most recent documentation push (much of which may apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and then use the child macro instead of the hard-coded list so Joe can continue his work. I am having a bit of a time with this, since I keep getting connection errors and "error retrieving breadcrumbs" problems. Is anyone else having trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org [talk-bounces@lists.collectionspace.orgmailto:talk-bounces@lists.collectionspace.org] on behalf of Joe Slag [joe@slagwerks.commailto:joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Jesse,
The wiki has been fine today. I will let you know if anything else crops up and am going to blame it on crappy free wifi for now.
Heather
From: Jesse Martinez [mailto:jmartinez@movingimage.us]
Sent: Thursday, September 15, 2011 3:09 PM
To: Heather Hart
Cc: Joe Slag; CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we be aware of any recent changes to 1.9. Although, I make the assumption that some changes may have occurred on both 1.8 as well as 1.9 so in that case it's moot. The trouble with links is a big one and if we can straighten it with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on. We just need to make the concerted effort to follow every lin on every page to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was this recently? Did you also see issues with jira or any of our other services?
- Jesse
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart <hhart@bpoc.org<mailto:hhart@bpoc.org>> wrote:
Hi Joe,
One documentation issue always leads to several dozen more. This is really two separate problems.
First of all, these pages were not copied over because at the time the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued these pages from the main wiki where they were buried. If you look at the 1.9 wiki space, these pages have been moved over and appear in the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9 wiki, the links are still broken. The links did not travel well because they are hard-linked (it is linked as a standard hyperlink: http://wiki.collectionspace.org/display/collectionspace/How+to+change+the+definition+of+a+field+in+the+Services+configuration) so when we "rescued" these pages, it also broke these links. Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links. This is a great reminder to everyone to use the fluid tools when editing the wiki pages. In this particular case, there is a child pages macro that would work perfectly. Under normal circumstances it is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty bad shape in general. Jesse, what do you think about re-mirroring the 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages. The 1.9 wiki will include the "rescued" pages, but would not include the fruits of our most recent documentation push (much of which may apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and then use the child macro instead of the hard-coded list so Joe can continue his work. I am having a bit of a time with this, since I keep getting connection errors and "error retrieving breadcrumbs" problems. Is anyone else having trouble with the wiki?
Heather
________________________________________
From: talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org> [talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org>] on behalf of Joe Slag [joe@slagwerks.com<mailto:joe@slagwerks.com>]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
and noticed that many of the details, under the heading "Procedure
step checklist", are links to pages that have been moved or
deprectated.
For example, http://wiki.collectionspace.org/display/collectionspace/How+to+edit+the+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema+file
is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
_______________________________________________
Talk mailing list
Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org>
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
HH
Heather Hart
Tue, Sep 20, 2011 12:58 AM
Hi Aron,
Can you take a look at the updated multivalued field 1.8 pages and add in the necessary details about the minibuild?
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
Also a general review for accuracy as of 1.8 would be great. Rick has given it a once over already.
Thanks,
Heather
-----Original Message-----
From: Aron Roberts [mailto:aronroberts@gmail.com]
Sent: Thursday, September 15, 2011 3:51 PM
To: Jesse Martinez; Heather Hart
Cc: CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
PLEASE READ before 'mirroring' any docs
Many of the key v1.8 docs are very different than their v1.9 counterparts:
-
Some of the Installing CollectionSpace docs for v1.8 are (at least) slightly different than their 1.9 counterparts.
-
At least one or two of the core Configuring CollectionSpace docs differ substantially from their 1.9 counterparts, to reflect that the app layer configuration changed to a new overlay structure in v1.9.
Before doing any wholesale 'mirroring', it might be good to check a chronological list of recently updated documents, and/or review which documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez jmartinez@movingimage.us wrote:
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that we
be aware of any recent changes to 1.9. Although, I make the assumption
that some changes may have occurred on both 1.8 as well as 1.9 so in
that case it's moot. The trouble with links is a big one and if we can
straighten it with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
We just need to make the concerted effort to follow every lin on every
page to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was
this recently? Did you also see issues with jira or any of our other services?
- Jesse
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart hhart@bpoc.org wrote:
Hi Joe,
One documentation issue always leads to several dozen more. This is
really two separate problems.
First of all, these pages were not copied over because at the time
the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued
these pages from the main wiki where they were buried. If you look at
the 1.9 wiki space, these pages have been moved over and appear in
the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9
wiki, the links are still broken. The links did not travel well
because they are hard-linked (it is linked as a standard hyperlink:
http://wiki.collectionspace.org/display/collectionspace/How+to+change
+the+definition+of+a+field+in+the+Services+configuration)
so when we "rescued" these pages, it also broke these links.
Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links.
This is a great reminder to everyone to use the fluid tools when
editing the wiki pages. In this particular case, there is a child
pages macro that would work perfectly. Under normal circumstances it
is best to link to another cspace wiki page by using the search function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty
bad shape in general. Jesse, what do you think about re-mirroring the
1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages.
The 1.9 wiki will include the "rescued" pages, but would not include
the fruits of our most recent documentation push (much of which may
apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and
then use the child macro instead of the hard-coded list so Joe can continue his work.
I am having a bit of a time with this, since I keep getting
connection errors and "error retrieving breadcrumbs" problems. Is
anyone else having trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org
[talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
[joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+
multivalued and noticed that many of the details, under the heading
"Procedure step checklist", are links to pages that have been moved
or deprectated.
For example,
http://wiki.collectionspace.org/display/collectionspace/How+to+edit+t
he+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema
+file is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti
onspace.org
Hi Aron,
Can you take a look at the updated multivalued field 1.8 pages and add in the necessary details about the minibuild?
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
Also a general review for accuracy as of 1.8 would be great. Rick has given it a once over already.
Thanks,
Heather
-----Original Message-----
From: Aron Roberts [mailto:aronroberts@gmail.com]
Sent: Thursday, September 15, 2011 3:51 PM
To: Jesse Martinez; Heather Hart
Cc: CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
*******PLEASE READ before 'mirroring' any docs*******
Many of the key v1.8 docs are very different than their v1.9 counterparts:
* Some of the Installing CollectionSpace docs for v1.8 are (at least) slightly different than their 1.9 counterparts.
* At least one or two of the core Configuring CollectionSpace docs differ substantially from their 1.9 counterparts, to reflect that the app layer configuration changed to a new overlay structure in v1.9.
Before doing any wholesale 'mirroring', it might be good to check a chronological list of recently updated documents, and/or review which documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez <jmartinez@movingimage.us> wrote:
> Heather,
> I think it's safe to mirror 1.9 onto 1.8 documentation granted that we
> be aware of any recent changes to 1.9. Although, I make the assumption
> that some changes may have occurred on both 1.8 as well as 1.9 so in
> that case it's moot. The trouble with links is a big one and if we can
> straighten it with 1.9 then we'd all be better off since we'll use 1.9 for 1.11 and so on.
> We just need to make the concerted effort to follow every lin on every
> page to make sure it's pointing in the right location.
> I'm not aware of any time out issues for me/us on the east coast. Was
> this recently? Did you also see issues with jira or any of our other services?
> - Jesse
>
> On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart <hhart@bpoc.org> wrote:
>>
>> Hi Joe,
>>
>> One documentation issue always leads to several dozen more. This is
>> really two separate problems.
>>
>> First of all, these pages were not copied over because at the time
>> the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued
>> these pages from the main wiki where they were buried. If you look at
>> the 1.9 wiki space, these pages have been moved over and appear in
>> the heirarchy (left sidebar) under the appropriate page.
>>
>> Secondly, even though the pages exist where they should in the 1.9
>> wiki, the links are still broken. The links did not travel well
>> because they are hard-linked (it is linked as a standard hyperlink:
>> http://wiki.collectionspace.org/display/collectionspace/How+to+change
>> +the+definition+of+a+field+in+the+Services+configuration)
>> so when we "rescued" these pages, it also broke these links.
>> Unfortunately, the fluid tools can't tell us (as far as I know) when we break hard links.
>> This is a great reminder to everyone to use the fluid tools when
>> editing the wiki pages. In this particular case, there is a child
>> pages macro that would work perfectly. Under normal circumstances it
>> is best to link to another cspace wiki page by using the search function on the edit link screen.
>>
>> So, in terms of what we can and should do, the 1.8 wiki is in pretty
>> bad shape in general. Jesse, what do you think about re-mirroring the
>> 1.9 wiki into 1.8? This is risky if people have been making changes to the 1.8 pages.
>> The 1.9 wiki will include the "rescued" pages, but would not include
>> the fruits of our most recent documentation push (much of which may
>> apply to 1.8?).
>>
>> For now I am going to manually move these pages back into 1.8 and
>> then use the child macro instead of the hard-coded list so Joe can continue his work.
>> I am having a bit of a time with this, since I keep getting
>> connection errors and "error retrieving breadcrumbs" problems. Is
>> anyone else having trouble with the wiki?
>>
>> Heather
>> ________________________________________
>> From: talk-bounces@lists.collectionspace.org
>> [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
>> [joe@slagwerks.com]
>> Sent: Wednesday, September 14, 2011 8:10 AM
>> To: CollectionSpace Talk List
>> Subject: [Talk] changed / deprecated links in 1.8 docs
>>
>> I was just referring to
>>
>> http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+
>> multivalued and noticed that many of the details, under the heading
>> "Procedure step checklist", are links to pages that have been moved
>> or deprectated.
>>
>> For example,
>> http://wiki.collectionspace.org/display/collectionspace/How+to+edit+t
>> he+definition+of+data+passed+into+and+out+of+a+field+in+the+UI+schema
>> +file is linked to in step 2b. The top of that page says in red:
>>
>> REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
>> THE UI SCHEMA FILE)
>>
>> Many of the other pages seem to have been moved in a way that allows
>> confluence to make a good guess about their location, but still
>> presents an intermediate 'page moved' page.
>>
>> If this was just any old release I don't think it would be that
>> important, but I thought I'd mention it given 1.8's positioning as a
>> thoroughly-QA'd release. Also it might be nice to identify whatever
>> process problems led to this problem so that it can be avoided for
>> future releases.
>>
>> cheers,
>> Joe
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>>
>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti
>> onspace.org
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectio
> nspace.org
>
>
AS
Angela Spinazze
Tue, Sep 20, 2011 4:26 PM
Thanks Heather, Aron, Jesse, and Rick for your work on getting this
documentation sorted.
One question for you all: As I was talking with Joe S. last week, he
mentioned that he was trying to figure out where to put the WAC local
schema. Is there a designated place, for example, where the local
schema lives? Is that something that we cover in the documentation?
Thanks,
Angela
On Sep 19, 2011, at 7:58 PM, Heather Hart wrote:
Hi Aron,
Can you take a look at the updated multivalued field 1.8 pages and
add in the necessary details about the minibuild?
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
Also a general review for accuracy as of 1.8 would be great. Rick
has given it a once over already.
Thanks,
Heather
-----Original Message-----
From: Aron Roberts [mailto:aronroberts@gmail.com]
Sent: Thursday, September 15, 2011 3:51 PM
To: Jesse Martinez; Heather Hart
Cc: CollectionSpace Talk List
Subject: Re: [Talk] changed / deprecated links in 1.8 docs
PLEASE READ before 'mirroring' any docs
Many of the key v1.8 docs are very different than their v1.9
counterparts:
-
Some of the Installing CollectionSpace docs for v1.8 are (at
least) slightly different than their 1.9 counterparts.
-
At least one or two of the core Configuring CollectionSpace docs
differ substantially from their 1.9 counterparts, to reflect that
the app layer configuration changed to a new overlay structure in
v1.9.
Before doing any wholesale 'mirroring', it might be good to check a
chronological list of recently updated documents, and/or review
which documents should not be mirrored with both me and Kasper.
Thanks,
Aron
On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez <jmartinez@movingimage.us
wrote:
Heather,
I think it's safe to mirror 1.9 onto 1.8 documentation granted that
we
be aware of any recent changes to 1.9. Although, I make the
assumption
that some changes may have occurred on both 1.8 as well as 1.9 so in
that case it's moot. The trouble with links is a big one and if we
can
straighten it with 1.9 then we'd all be better off since we'll use
1.9 for 1.11 and so on.
We just need to make the concerted effort to follow every lin on
every
page to make sure it's pointing in the right location.
I'm not aware of any time out issues for me/us on the east coast. Was
this recently? Did you also see issues with jira or any of our
other services?
On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart hhart@bpoc.org wrote:
Hi Joe,
One documentation issue always leads to several dozen more. This is
really two separate problems.
First of all, these pages were not copied over because at the time
the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued
these pages from the main wiki where they were buried. If you look
at
the 1.9 wiki space, these pages have been moved over and appear in
the heirarchy (left sidebar) under the appropriate page.
Secondly, even though the pages exist where they should in the 1.9
wiki, the links are still broken. The links did not travel well
because they are hard-linked (it is linked as a standard hyperlink:
http://wiki.collectionspace.org/display/collectionspace/How+to
+change
+the+definition+of+a+field+in+the+Services+configuration)
so when we "rescued" these pages, it also broke these links.
Unfortunately, the fluid tools can't tell us (as far as I know)
when we break hard links.
This is a great reminder to everyone to use the fluid tools when
editing the wiki pages. In this particular case, there is a child
pages macro that would work perfectly. Under normal circumstances it
is best to link to another cspace wiki page by using the search
function on the edit link screen.
So, in terms of what we can and should do, the 1.8 wiki is in pretty
bad shape in general. Jesse, what do you think about re-mirroring
the
1.9 wiki into 1.8? This is risky if people have been making
changes to the 1.8 pages.
The 1.9 wiki will include the "rescued" pages, but would not include
the fruits of our most recent documentation push (much of which may
apply to 1.8?).
For now I am going to manually move these pages back into 1.8 and
then use the child macro instead of the hard-coded list so Joe can
continue his work.
I am having a bit of a time with this, since I keep getting
connection errors and "error retrieving breadcrumbs" problems. Is
anyone else having trouble with the wiki?
Heather
From: talk-bounces@lists.collectionspace.org
[talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
[joe@slagwerks.com]
Sent: Wednesday, September 14, 2011 8:10 AM
To: CollectionSpace Talk List
Subject: [Talk] changed / deprecated links in 1.8 docs
I was just referring to
http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a
+field+
multivalued and noticed that many of the details, under the heading
"Procedure step checklist", are links to pages that have been moved
or deprectated.
For example,
http://wiki.collectionspace.org/display/collectionspace/How+to+edit
+t
he+definition+of+data+passed+into+and+out+of+a+field+in+the+UI
+schema
+file is linked to in step 2b. The top of that page says in red:
REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
THE UI SCHEMA FILE)
Many of the other pages seem to have been moved in a way that allows
confluence to make a good guess about their location, but still
presents an intermediate 'page moved' page.
If this was just any old release I don't think it would be that
important, but I thought I'd mention it given 1.8's positioning as a
thoroughly-QA'd release. Also it might be nice to identify whatever
process problems led to this problem so that it can be avoided for
future releases.
cheers,
Joe
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/
talk_lists.collecti
onspace.org
Thanks Heather, Aron, Jesse, and Rick for your work on getting this
documentation sorted.
One question for you all: As I was talking with Joe S. last week, he
mentioned that he was trying to figure out where to put the WAC local
schema. Is there a designated place, for example, where the local
schema lives? Is that something that we cover in the documentation?
Thanks,
Angela
On Sep 19, 2011, at 7:58 PM, Heather Hart wrote:
> Hi Aron,
>
> Can you take a look at the updated multivalued field 1.8 pages and
> add in the necessary details about the minibuild?
>
> http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a+field+multivalued
>
> Also a general review for accuracy as of 1.8 would be great. Rick
> has given it a once over already.
>
> Thanks,
> Heather
>
> -----Original Message-----
> From: Aron Roberts [mailto:aronroberts@gmail.com]
> Sent: Thursday, September 15, 2011 3:51 PM
> To: Jesse Martinez; Heather Hart
> Cc: CollectionSpace Talk List
> Subject: Re: [Talk] changed / deprecated links in 1.8 docs
>
> *******PLEASE READ before 'mirroring' any docs*******
>
> Many of the key v1.8 docs are very different than their v1.9
> counterparts:
>
> * Some of the Installing CollectionSpace docs for v1.8 are (at
> least) slightly different than their 1.9 counterparts.
>
> * At least one or two of the core Configuring CollectionSpace docs
> differ substantially from their 1.9 counterparts, to reflect that
> the app layer configuration changed to a new overlay structure in
> v1.9.
>
> Before doing any wholesale 'mirroring', it might be good to check a
> chronological list of recently updated documents, and/or review
> which documents should not be mirrored with both me and Kasper.
>
> Thanks,
> Aron
>
> On Thu, Sep 15, 2011 at 3:08 PM, Jesse Martinez <jmartinez@movingimage.us
> > wrote:
>> Heather,
>> I think it's safe to mirror 1.9 onto 1.8 documentation granted that
>> we
>> be aware of any recent changes to 1.9. Although, I make the
>> assumption
>> that some changes may have occurred on both 1.8 as well as 1.9 so in
>> that case it's moot. The trouble with links is a big one and if we
>> can
>> straighten it with 1.9 then we'd all be better off since we'll use
>> 1.9 for 1.11 and so on.
>> We just need to make the concerted effort to follow every lin on
>> every
>> page to make sure it's pointing in the right location.
>> I'm not aware of any time out issues for me/us on the east coast. Was
>> this recently? Did you also see issues with jira or any of our
>> other services?
>> - Jesse
>>
>> On Thu, Sep 15, 2011 at 3:26 PM, Heather Hart <hhart@bpoc.org> wrote:
>>>
>>> Hi Joe,
>>>
>>> One documentation issue always leads to several dozen more. This is
>>> really two separate problems.
>>>
>>> First of all, these pages were not copied over because at the time
>>> the 1.8 wiki was mirrored from UNRELEASED, we had not yet rescued
>>> these pages from the main wiki where they were buried. If you look
>>> at
>>> the 1.9 wiki space, these pages have been moved over and appear in
>>> the heirarchy (left sidebar) under the appropriate page.
>>>
>>> Secondly, even though the pages exist where they should in the 1.9
>>> wiki, the links are still broken. The links did not travel well
>>> because they are hard-linked (it is linked as a standard hyperlink:
>>> http://wiki.collectionspace.org/display/collectionspace/How+to
>>> +change
>>> +the+definition+of+a+field+in+the+Services+configuration)
>>> so when we "rescued" these pages, it also broke these links.
>>> Unfortunately, the fluid tools can't tell us (as far as I know)
>>> when we break hard links.
>>> This is a great reminder to everyone to use the fluid tools when
>>> editing the wiki pages. In this particular case, there is a child
>>> pages macro that would work perfectly. Under normal circumstances it
>>> is best to link to another cspace wiki page by using the search
>>> function on the edit link screen.
>>>
>>> So, in terms of what we can and should do, the 1.8 wiki is in pretty
>>> bad shape in general. Jesse, what do you think about re-mirroring
>>> the
>>> 1.9 wiki into 1.8? This is risky if people have been making
>>> changes to the 1.8 pages.
>>> The 1.9 wiki will include the "rescued" pages, but would not include
>>> the fruits of our most recent documentation push (much of which may
>>> apply to 1.8?).
>>>
>>> For now I am going to manually move these pages back into 1.8 and
>>> then use the child macro instead of the hard-coded list so Joe can
>>> continue his work.
>>> I am having a bit of a time with this, since I keep getting
>>> connection errors and "error retrieving breadcrumbs" problems. Is
>>> anyone else having trouble with the wiki?
>>>
>>> Heather
>>> ________________________________________
>>> From: talk-bounces@lists.collectionspace.org
>>> [talk-bounces@lists.collectionspace.org] on behalf of Joe Slag
>>> [joe@slagwerks.com]
>>> Sent: Wednesday, September 14, 2011 8:10 AM
>>> To: CollectionSpace Talk List
>>> Subject: [Talk] changed / deprecated links in 1.8 docs
>>>
>>> I was just referring to
>>>
>>> http://wiki.collectionspace.org/display/CSPACE18/How+to+make+a
>>> +field+
>>> multivalued and noticed that many of the details, under the heading
>>> "Procedure step checklist", are links to pages that have been moved
>>> or deprectated.
>>>
>>> For example,
>>> http://wiki.collectionspace.org/display/collectionspace/How+to+edit
>>> +t
>>> he+definition+of+data+passed+into+and+out+of+a+field+in+the+UI
>>> +schema
>>> +file is linked to in step 2b. The top of that page says in red:
>>>
>>> REMOVE THIS PAGE - IT IS NOT ACCURATE. (FIELDS ARE NOT EDITED VIA
>>> THE UI SCHEMA FILE)
>>>
>>> Many of the other pages seem to have been moved in a way that allows
>>> confluence to make a good guess about their location, but still
>>> presents an intermediate 'page moved' page.
>>>
>>> If this was just any old release I don't think it would be that
>>> important, but I thought I'd mention it given 1.8's positioning as a
>>> thoroughly-QA'd release. Also it might be nice to identify whatever
>>> process problems led to this problem so that it can be avoided for
>>> future releases.
>>>
>>> cheers,
>>> Joe
>>>
>>> _______________________________________________
>>> Talk mailing list
>>> Talk@lists.collectionspace.org
>>>
>>> http://lists.collectionspace.org/mailman/listinfo/
>>> talk_lists.collecti
>>> onspace.org
>>
>>
>> _______________________________________________
>> Talk mailing list
>> Talk@lists.collectionspace.org
>> http://lists.collectionspace.org/mailman/listinfo/
>> talk_lists.collectio
>> nspace.org
>>
>>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
